@contrast/metrics
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate handoff to a trusted Contrast org publisher with strong track record. | ai | |
| dependencies | unvetted-dep:@contrast/otel | AI (dependencies): First-party sibling package from same Contrast Security monorepo/publisher. | ai | |
| provenance | no-provenance | AI (provenance): Contrast Security internal package; provenance not published for this org's packages consistently. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 1.43.0 | 8 / 0 | |
| 1.42.0 | 5 / 0 | |
| 1.41.0 | 5 / 0 | |
| 1.40.3 | 5 / 0 | |
| 1.40.2 | 5 / 0 | |
| 1.40.1 | 5 / 0 | |
| 1.40.0 | 5 / 0 | |
| 1.39.1 | 5 / 0 | |
| 1.39.0 | 5 / 0 | |
| 1.38.0 | 5 / 0 | |
| 1.37.1 | 5 / 0 | |
| 1.37.0 | 5 / 0 | |
| 1.36.1 | 5 / 0 | |
| 1.36.0 | 5 / 0 | |
| 1.35.0 | 5 / 0 | |
| 1.34.1 | 5 / 0 | |
| 1.34.0 | 5 / 0 | |
| 1.33.0 | 5 / 0 | |
| 1.32.0 | 5 / 0 | |
| 1.31.2 | 5 / 0 | |
| 1.31.1 | 5 / 0 | |
| 1.31.0 | 5 / 0 | |
| 1.30.0 | 5 / 0 | |
| 1.29.0 | 5 / 0 | |
| 1.28.0 | 5 / 0 | |
| 1.27.0 | 5 / 0 | |
| 1.26.0 | 5 / 0 | |
| 1.25.0 | 5 / 0 | |
| 1.24.0 | 5 / 0 | |
| 1.23.0 | 5 / 0 | |
| 1.22.2 | 5 / 0 | |
| 1.22.1 | 5 / 0 | |
| 1.22.0 | 5 / 0 | |
| 1.21.0 | 5 / 0 | |
| 1.20.0 | 5 / 0 | |
| 1.19.0 | 5 / 0 | |
| 1.18.0 | 5 / 0 | |
| 1.17.0 | 5 / 0 | |
| 1.16.0 | 5 / 0 | |
| 1.15.0 | 5 / 0 | |
| 1.14.0 | 5 / 0 | |
| 1.13.0 | 5 / 0 | |
| 1.12.0 | 5 / 0 | |
| 1.11.1 | 5 / 0 | |
| 1.11.0 | 1 / 0 | |
| 1.10.0 | 1 / 0 | |
| 1.9.0 | 1 / 0 | |
| 1.8.3 | 1 / 0 | |
| 1.8.2 | 1 / 0 | |
| 1.8.1 | 1 / 0 | |
| 1.8.0 | 1 / 0 |
v1.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.