@mui/core-downloads-tracker
Internal package to track number of downloads of our design system libraries.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): mui-release-bot is a standard CI/CD release automation account for the MUI monorepo; this addition is expected and benign for this package. | ai | |
| provenance | missing-githead | AI (provenance): MUI internal tracker package with no code; missing gitHead reflects publish tooling change, not a security concern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): This is an intentionally near-empty internal MUI tracking package; tiny payload, no deps, no README code are all by design. | ai | |
| provenance | publisher-changed | AI (provenance): MUI team rotates which member publishes releases; both siriwatknp and mj12albert are established MUI contributors. | ai |
Versions (showing 51 of 156)
| Version | Deps | Published |
|---|---|---|
| 9.0.1 | 0 / 0 | |
| 9.0.0 | 0 / 0 | |
| 7.3.11 | 0 / 0 | |
| 7.3.10 | 0 / 0 | |
| 7.3.9 | 0 / 0 | |
| 7.3.8 | 0 / 0 | |
| 7.3.7 | 0 / 0 | |
| 7.3.6 | 0 / 0 | |
| 7.3.5 | 0 / 0 | |
| 7.3.4 | 0 / 0 | |
| 7.3.3 | 0 / 0 | |
| 7.3.2 | 0 / 0 | |
| 7.3.1 | 0 / 0 | |
| 7.3.0 | 0 / 0 | |
| 7.2.0 | 0 / 0 | |
| 7.1.2 | 0 / 0 | |
| 7.1.1 | 0 / 0 | |
| 7.1.0 | 0 / 0 | |
| 7.0.2 | 0 / 0 | |
| 7.0.1 | 0 / 0 | |
| 7.0.0 | 0 / 0 | |
| 6.5.0 | 0 / 0 | |
| 6.4.12 | 0 / 0 | |
| 6.4.11 | 0 / 0 | |
| 6.4.10 | 0 / 0 | |
| 6.4.9 | 0 / 0 | |
| 6.4.8 | 0 / 0 | |
| 6.4.7 | 0 / 0 | |
| 6.4.6 | 0 / 0 | |
| 6.4.5 | 0 / 0 | |
| 6.4.4 | 0 / 0 | |
| 6.4.3 | 0 / 0 | |
| 6.4.2 | 0 / 0 | |
| 6.4.1 | 0 / 0 | |
| 6.4.0 | 0 / 0 | |
| 6.3.1 | 0 / 0 | |
| 6.3.0 | 0 / 0 | |
| 6.2.1 | 0 / 0 | |
| 6.2.0 | 0 / 0 | |
| 6.1.10 | 0 / 0 | |
| 6.1.9 | 0 / 0 | |
| 6.1.8 | 0 / 0 | |
| 6.1.7 | 0 / 0 | |
| 6.1.6 | 0 / 0 | |
| 6.1.5 | 0 / 0 | |
| 6.1.4 | 0 / 0 | |
| 6.1.3 | 0 / 0 | |
| 6.1.2 | 0 / 0 | |
| 6.1.1 | 0 / 0 | |
| 6.1.0 | 0 / 0 | |
| 6.0.2 | 0 / 0 |
v9.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.3
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This 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.
v7.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
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.2
2 findingsThis version was published by a different npm account than previous versions on 2025-06-19. 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.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.2
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.0.1
2 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.
v7.0.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.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.11
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.
v6.4.10
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: aarongarciah.
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-31. This could indicate a legitimate maintainer transition or an account compromise.
v6.4.9
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-25. This could indicate a legitimate maintainer transition or an account compromise.
v6.4.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 2025-03-17. This could indicate a legitimate maintainer transition or an account compromise.
v6.4.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 2025-03-05. This could indicate a legitimate maintainer transition or an account compromise.
v6.4.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 2025-02-26. This could indicate a legitimate maintainer transition or an account compromise.
v6.4.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 2025-02-18. This could indicate a legitimate maintainer transition or an account compromise.
v6.4.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 2025-02-11. This could indicate a legitimate maintainer transition or an account compromise.
v6.4.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 2025-02-04. This could indicate a legitimate maintainer transition or an account compromise.
v6.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.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 2025-01-21. This could indicate a legitimate maintainer transition or an account compromise.
v6.4.0
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-01-14. This could indicate a legitimate maintainer transition or an account compromise.
v6.3.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 2025-01-03. This could indicate a legitimate maintainer transition or an account compromise.
v6.3.0
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-23. This could indicate a legitimate maintainer transition or an account compromise.
v6.2.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 2024-12-17. This could indicate a legitimate maintainer transition or an account compromise.
v6.2.0
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-11. This could indicate a legitimate maintainer transition or an account compromise.
v6.1.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 2024-12-04. This could indicate a legitimate maintainer transition or an account compromise.
v6.1.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 2024-11-27. This could indicate a legitimate maintainer transition or an account compromise.
v6.1.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 2024-11-20. This could indicate a legitimate maintainer transition or an account compromise.
v6.1.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 2024-11-13. This could indicate a legitimate maintainer transition or an account compromise.
v6.1.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 2024-10-30. This could indicate a legitimate maintainer transition or an account compromise.
v6.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 2024-10-22. This could indicate a legitimate maintainer transition or an account compromise.
v6.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
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-09-11. This could indicate a legitimate maintainer transition or an account compromise.
v6.0.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 2024-09-03. This could indicate a legitimate maintainer transition or an account compromise.