@peculiar/color
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 | publisher-changed | AI (provenance): Publisher is GitHub Actions with SLSA provenance; CI/CD publishing is the documented pattern for PeculiarVentures packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo package published infrequently; SLSA attestation and unchanged scripts/deps confirm legitimate publish. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.8.10 | 0 / 1 | |
| 0.1.10 | 0 / 1 | |
| 0.1.9 | 0 / 1 | |
| 0.1.8 | 0 / 2 | |
| 0.1.7 | 0 / 2 | |
| 0.1.6 | 0 / 2 |
v1.8.10
2 findingsThis version was published by a different npm account than previous versions on 2026-05-29. 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.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.