@capsizecss/metrics
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): CI account migration with SLSA attestation preserved; benign. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Generated font-metrics collection is the package's core data output. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Font metrics data growth; no injected/exec payload. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 0 / 8 | |
| 4.1.0 | 0 / 8 | |
| 4.0.0 | 0 / 8 | |
| 3.7.0 | 0 / 8 | |
| 3.6.2 | 0 / 8 | |
| 3.6.1 | 0 / 8 | |
| 3.6.0 | 0 / 8 | |
| 3.1.0 | 0 / 11 | |
| 3.0.0 | 0 / 11 |
v4.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.1
2 findingsThis version was published by a different npm account than previous versions on 2025-11-12. 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.
v3.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.