@mui/utils
Utility functions for React components.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/react-is | AI (dependencies): @types/react-is is a standard DefinitelyTyped type definition package; its inclusion as a dependency in a TypeScript utility library is expected and benign across all versions. | ai | |
| phantom-deps | phantom-dep:@types/react-is | AI (phantom-deps): Type-only @types/* packages are conventionally declared as deps without direct imports; consumed by TypeScript at compile time. Stable false positive for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of mbrookes and mui-release-bot aligns with MUI's transition to GitHub Actions provenance-based publishing. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed from human (siriwatknp) to GitHub Actions CI/CD with SLSA provenance — expected for MUI's automated release pipeline. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): janpotoms is a known MUI core team member; legitimate maintainer list update. | ai | |
| dependencies | unvetted-dep:@types/prop-types | AI (dependencies): @types/prop-types is a standard TypeScript definitions package; unvetted status is expected for type definitions and poses no security risk. | ai | |
| phantom-deps | phantom-dep:@types/prop-types | AI (phantom-deps): Type definitions are framework-scoped and loaded by convention; phantom dependency status is expected and benign. | ai |
Versions (showing 30 of 130)
| Version | Deps | Published |
|---|---|---|
| 5.11.1 | 5 / 0 | |
| 5.11.0 | 5 / 0 | |
| 5.10.16 | 5 / 0 | |
| 5.10.15 | 5 / 0 | |
| 5.10.14 | 5 / 0 | |
| 5.10.9 | 5 / 0 | |
| 5.10.6 | 5 / 0 | |
| 5.10.3 | 5 / 0 | |
| 5.9.3 | 5 / 0 | |
| 5.9.1 | 5 / 0 | |
| 5.9.0 | 5 / 0 | |
| 5.8.6 | 5 / 0 | |
| 5.8.4 | 5 / 0 | |
| 5.8.0 | 5 / 0 | |
| 5.7.0 | 5 / 0 | |
| 5.6.1 | 5 / 0 | |
| 5.6.0 | 5 / 0 | |
| 5.5.3 | 5 / 0 | |
| 5.4.4 | 5 / 0 | |
| 5.4.2 | 5 / 0 | |
| 5.4.1 | 5 / 0 | |
| 5.3.0 | 5 / 0 | |
| 5.2.3 | 5 / 0 | |
| 5.2.2 | 5 / 0 | |
| 5.2.1 | 5 / 0 | |
| 5.2.0 | 5 / 0 | |
| 5.1.1 | 5 / 0 | |
| 5.1.0 | 5 / 0 | |
| 5.0.1 | 5 / 0 | |
| 5.0.0 | 5 / 0 |
v5.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.