@contrast/scopes
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@contrast/logger | AI (phantom-deps): Same-org monorepo dep; likely re-exported or used transitively, not a direct import. | ai | |
| phantom-deps | phantom-dep:@contrast/patcher | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@contrast/dep-hooks | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 1.36.0 | 4 / 0 | |
| 1.35.0 | 4 / 0 | |
| 1.34.0 | 4 / 0 | |
| 1.33.3 | 4 / 0 | |
| 1.30.1 | 4 / 0 | |
| 1.30.0 | 4 / 0 | |
| 1.29.1 | 4 / 0 | |
| 1.29.0 | 4 / 0 | |
| 1.28.0 | 4 / 0 | |
| 1.27.1 | 4 / 0 | |
| 1.27.0 | 4 / 0 | |
| 1.26.0 | 4 / 0 | |
| 1.25.0 | 4 / 0 | |
| 1.24.2 | 4 / 0 | |
| 1.24.1 | 4 / 0 | |
| 1.24.0 | 4 / 0 | |
| 1.23.0 | 4 / 0 | |
| 1.22.0 | 4 / 0 | |
| 1.21.0 | 4 / 0 | |
| 1.20.0 | 4 / 0 | |
| 1.19.0 | 4 / 0 | |
| 1.18.0 | 4 / 0 | |
| 1.17.0 | 3 / 0 | |
| 1.16.0 | 3 / 0 | |
| 1.15.2 | 3 / 0 | |
| 1.15.1 | 3 / 0 | |
| 1.15.0 | 3 / 0 | |
| 1.14.0 | 3 / 0 | |
| 1.13.0 | 3 / 0 | |
| 1.12.0 | 3 / 0 | |
| 1.11.0 | 3 / 0 | |
| 1.10.0 | 3 / 0 | |
| 1.9.0 | 3 / 0 | |
| 1.8.0 | 3 / 0 | |
| 1.7.0 | 3 / 0 | |
| 1.6.0 | 3 / 0 | |
| 1.5.0 | 3 / 0 | |
| 1.4.2 | 3 / 0 |
v1.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.