@material/material-color-utilities
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): google-wombot is npm's official publish-proxy account for Google org packages, not a hijack. | ai | |
| provenance | publisher-changed-stale | AI (provenance): google-wombot is Google's standard wombat-dressing-room publish account for this org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same wombat-dressing-room account addition, consistent with Google publishing infra. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 0 / 5 | |
| 0.3.0 | 0 / 5 | |
| 0.2.7 | 0 / 5 | |
| 0.2.6 | 0 / 5 | |
| 0.2.5 | 0 / 5 | |
| 0.2.4 | 0 / 5 | |
| 0.2.3 | 0 / 5 | |
| 0.2.2 | 0 / 4 | |
| 0.2.0 | 0 / 3 | |
| 0.1.2 | 0 / 3 | |
| 0.1.1 | 0 / 3 | |
| 0.1.0 | 0 / 3 |
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
2 findingsThis version was published by a different npm account (google-wombot) than the most recent previously approved version (guidezpl) on 2023-06-28. It has since remained available on npm for 1123 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
2 findingsThis version was published by a different npm account (google-wombot) than the most recent previously approved version (guidezpl) on 2023-04-27. It has since remained available on npm for 1185 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
2 findingsThis version was published by a different npm account (google-wombot) than the most recent previously approved version (guidezpl) on 2023-04-15. It has since remained available on npm for 1198 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
2 findingsThis version was published by a different npm account (google-wombot) than the most recent previously approved version (guidezpl) on 2023-03-07. It has since remained available on npm for 1236 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
2 findingsThis version was published by a different npm account (google-wombot) than the most recent previously approved version (guidezpl) on 2023-03-03. It has since remained available on npm for 1240 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
2 findingsThis version was published by a different npm account (google-wombot) than the most recent previously approved version (guidezpl) on 2023-03-02. It has since remained available on npm for 1241 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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: google-wombot.
This version was published by a different npm account (google-wombot) than the most recent previously approved version (guidezpl) on 2022-08-05. It has since remained available on npm for 1450 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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: google-wombot.
This version was published by a different npm account (google-wombot) than the most recent previously approved version (guidezpl) on 2022-04-21. It has since remained available on npm for 1556 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.