@mui/types
Utility types for Material UI.
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): MUI types package ships only .d.ts files; publisher diegoandai is established MUI maintainer. Missing gitHead on backport branch is benign. | ai | |
| provenance | publisher-changed | AI (provenance): MUI migrated from human publisher (siriwatknp) to GitHub Actions CI/CD. SLSA provenance confirms legitimate automated publishing. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine team roster change for a large org (MUI). No signs of takeover. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped runtime dependency loaded by convention via Babel transforms; standard for MUI packages. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 9.0.0 | 1 / 0 | |
| 7.4.12 | 1 / 0 | |
| 7.4.11 | 1 / 0 | |
| 7.4.10 | 1 / 0 | |
| 7.4.9 | 1 / 0 | |
| 7.4.8 | 1 / 0 | |
| 7.4.7 | 1 / 0 | |
| 7.4.6 | 1 / 0 | |
| 7.4.5 | 1 / 0 | |
| 7.4.4 | 1 / 0 | |
| 7.4.3 | 1 / 0 | |
| 7.4.2 | 1 / 0 | |
| 7.4.1 | 1 / 0 | |
| 7.4.0 | 1 / 0 | |
| 7.3.1 | 1 / 0 | |
| 7.3.0 | 1 / 0 | |
| 7.2.24 | 0 / 0 | |
| 7.2.23 | 0 / 0 | |
| 7.2.22 | 0 / 0 | |
| 7.2.21 | 0 / 0 | |
| 7.2.20 | 0 / 0 | |
| 7.2.19 | 0 / 0 | |
| 7.2.18 | 0 / 0 | |
| 7.2.17 | 0 / 0 | |
| 7.2.16 | 0 / 0 | |
| 7.2.15 | 0 / 0 | |
| 7.2.14 | 0 / 0 | |
| 7.2.13 | 0 / 0 | |
| 7.2.12 | 0 / 0 | |
| 7.2.11 | 0 / 0 | |
| 7.2.10 | 0 / 0 | |
| 7.2.9 | 0 / 0 | |
| 7.2.8 | 0 / 0 | |
| 7.2.7 | 0 / 0 | |
| 7.2.6 | 0 / 0 | |
| 7.2.5 | 0 / 0 | |
| 7.2.4 | 0 / 0 | |
| 7.2.3 | 0 / 0 | |
| 7.2.2 | 0 / 0 | |
| 7.2.1 | 0 / 0 | |
| 7.2.0 | 0 / 0 | |
| 7.1.5 | 0 / 0 | |
| 7.1.4 | 0 / 0 | |
| 7.1.3 | 0 / 0 | |
| 7.1.2 | 0 / 0 | |
| 7.1.1 | 0 / 0 | |
| 7.1.0 | 0 / 0 | |
| 7.0.0 | 0 / 0 |
v7.4.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.4.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.4.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.4.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.4.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.4.7
2 findingsThis version was published by a different npm account than previous versions on 2025-10-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mj12albert.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-04-09. This could indicate a legitimate maintainer transition or an account compromise.
v7.4.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: siriwatknp.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-03-26. This could indicate a legitimate maintainer transition or an account compromise.
v7.3.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: siriwatknp.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-03-19. This could indicate a legitimate maintainer transition or an account compromise.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.24
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: diegoandai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-03-17. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.23
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-03-05. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.20
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-12-17. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.19
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-10-30. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.18
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-10-09. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.16
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-08-27. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.14
3 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mnajdova.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-03-19. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.13
3 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: siriwatknp.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-01-10. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-01-03. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.11
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-12-12. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.10
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-11-29. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-11-14. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-10-31. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-10-24. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-10-10. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-10-04. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-04-11. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: michaldudak.
v7.2.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-11-28. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-25. This could indicate a legitimate maintainer transition or an account compromise.
v7.1.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-06-14. This could indicate a legitimate maintainer transition or an account compromise.
v7.1.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-14. This could indicate a legitimate maintainer transition or an account compromise.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-02-08. This could indicate a legitimate maintainer transition or an account compromise.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.