@contrast/instrumentation
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@contrast/logger | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo-style packages. | ai | |
| phantom-deps | phantom-dep:@contrast/patcher | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo-style packages. | ai | |
| phantom-deps | phantom-dep:@contrast/dep-hooks | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo-style packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal enterprise tooling; sparse metadata is consistent across all @contrast org packages. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.42.3 | 4 / 0 | |
| 1.42.2 | 4 / 0 | |
| 1.39.1 | 4 / 0 | |
| 1.39.0 | 4 / 0 | |
| 1.38.1 | 4 / 0 | |
| 1.38.0 | 4 / 0 | |
| 1.37.0 | 4 / 0 | |
| 1.36.1 | 4 / 0 | |
| 1.36.0 | 4 / 0 | |
| 1.35.0 | 4 / 0 | |
| 1.34.0 | 4 / 0 | |
| 1.33.2 | 4 / 0 | |
| 1.33.1 | 4 / 0 | |
| 1.33.0 | 4 / 0 | |
| 1.32.0 | 4 / 0 | |
| 1.31.0 | 4 / 0 | |
| 1.30.0 | 4 / 0 |
v1.42.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.