@material-ui/styles
Material-UI Styles - The styling solution of Material-UI.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): oliviertassinari and eps1lon are both core MUI team members; intra-team publisher rotation is expected for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Adding MUI team members as maintainers is routine organizational activity for this package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 4.11.5 | 16 / 0 | |
| 4.11.4 | 16 / 0 | |
| 4.11.3 | 16 / 0 | |
| 4.11.2 | 16 / 0 | |
| 4.11.1 | 16 / 0 | |
| 4.10.0 | 16 / 0 | |
| 4.9.14 | 16 / 0 | |
| 4.9.13 | 16 / 0 | |
| 4.9.10 | 16 / 0 | |
| 4.9.6 | 16 / 0 | |
| 4.9.0 | 16 / 0 | |
| 4.8.2 | 16 / 0 | |
| 4.7.1 | 16 / 0 | |
| 4.6.0 | 16 / 0 | |
| 4.5.2 | 16 / 0 | |
| 4.5.0 | 17 / 0 | |
| 4.4.3 | 17 / 0 | |
| 4.4.1 | 18 / 0 | |
| 4.3.3 | 18 / 0 | |
| 4.3.0 | 18 / 0 | |
| 4.2.1 | 18 / 0 | |
| 4.2.0 | 18 / 0 | |
| 4.1.2 | 18 / 0 | |
| 4.1.1 | 18 / 0 | |
| 4.1.0 | 18 / 0 | |
| 4.0.2 | 17 / 0 | |
| 4.0.1 | 17 / 0 | |
| 4.0.0 | 17 / 0 |
v4.11.4
2 findingsThis version was published by a different npm account than previous versions on 2021-04-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.10
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.0
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.7.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.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.1
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.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.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.