@material-ui/core
React components that implement Google's Material Design.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Internal package swap within trusted MUI org, not an external supply-chain risk. | ai | |
| dependencies | unvetted-dep:@material-ui/react-transition-group | AI (dependencies): Official @material-ui scoped fork of react-transition-group, maintained by same org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mnajdova, siriwatknp, michaldudak are known MUI team members. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Reflects normal MUI team roster changes during v4→v5 transition. | ai | |
| provenance | publisher-changed | AI (provenance): eps1lon is a known MUI core maintainer; legitimate team transition from oliviertassinari. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Expected: v4 was in maintenance mode while v5 was developed. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Gap between compared versions (4.9.4→4.12.3) explains new files; no injected code. | ai | |
| phantom-deps | phantom-dep:@types/react-transition-group | AI (phantom-deps): TypeScript type-only packages being declared but not directly imported is a standard pattern; no security concern for this package. | ai | |
| dependencies | unvetted-dep:react-transition-group | AI (dependencies): react-transition-group is a well-known React community library and a documented, expected dependency of @material-ui/core. Stable across versions. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @material-ui/core is a major scoped React UI library with no relation to the 'cors' package; Levenshtein match is a false positive. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 4.12.3 | 12 / 0 | |
| 4.9.7 | 12 / 0 | |
| 4.9.6 | 12 / 0 | |
| 4.9.5 | 12 / 0 | |
| 4.9.4 | 12 / 0 | |
| 4.9.3 | 13 / 0 | |
| 4.9.2 | 14 / 0 | |
| 4.9.1 | 14 / 0 | |
| 4.9.0 | 14 / 0 | |
| 4.8.3 | 14 / 0 | |
| 4.8.2 | 14 / 0 | |
| 4.8.1 | 14 / 0 | |
| 4.8.0 | 14 / 0 | |
| 4.7.2 | 14 / 0 | |
| 4.7.1 | 14 / 0 | |
| 4.7.0 | 13 / 0 | |
| 4.6.1 | 13 / 0 | |
| 4.6.0 | 13 / 0 | |
| 4.5.2 | 13 / 0 | |
| 4.5.1 | 15 / 0 | |
| 4.5.0 | 15 / 0 | |
| 4.4.3 | 15 / 0 | |
| 4.4.2 | 16 / 0 | |
| 4.4.1 | 16 / 0 | |
| 4.4.0 | 16 / 0 | |
| 4.3.3 | 16 / 0 | |
| 4.3.2 | 16 / 0 | |
| 4.3.1 | 16 / 0 | |
| 4.3.0 | 16 / 0 | |
| 4.2.1 | 16 / 0 | |
| 4.2.0 | 16 / 0 | |
| 4.1.3 | 18 / 0 | |
| 4.1.2 | 18 / 0 | |
| 4.1.1 | 18 / 0 | |
| 4.1.0 | 18 / 0 | |
| 4.0.2 | 19 / 0 | |
| 4.0.1 | 19 / 0 | |
| 4.0.0 | 19 / 0 |
v4.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.