@contrast/rewriter
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/core | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for internal monorepo packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Contrast Security enterprise tooling; sparse public metadata is expected for internal instrumentation packages. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 1.43.0 | 7 / 0 | |
| 1.42.0 | 7 / 0 | |
| 1.41.0 | 7 / 0 | |
| 1.40.4 | 7 / 0 | |
| 1.40.3 | 7 / 0 | |
| 1.40.2 | 7 / 0 | |
| 1.37.2 | 8 / 0 | |
| 1.37.1 | 8 / 0 | |
| 1.37.0 | 6 / 0 | |
| 1.36.1 | 6 / 0 | |
| 1.36.0 | 6 / 0 | |
| 1.35.0 | 6 / 0 | |
| 1.34.0 | 6 / 0 | |
| 1.33.0 | 6 / 0 | |
| 1.32.0 | 6 / 0 | |
| 1.31.0 | 6 / 0 | |
| 1.30.2 | 6 / 0 | |
| 1.30.1 | 6 / 0 | |
| 1.30.0 | 6 / 0 | |
| 1.29.0 | 6 / 0 | |
| 1.28.0 | 6 / 0 | |
| 1.27.0 | 6 / 0 | |
| 1.26.0 | 6 / 0 | |
| 1.25.0 | 6 / 0 | |
| 1.24.0 | 6 / 0 | |
| 1.23.0 | 6 / 0 | |
| 1.22.0 | 6 / 0 | |
| 1.21.4 | 6 / 0 | |
| 1.21.3 | 6 / 0 | |
| 1.21.2 | 6 / 0 | |
| 1.21.1 | 6 / 0 | |
| 1.21.0 | 6 / 0 | |
| 1.20.0 | 6 / 0 | |
| 1.19.0 | 6 / 0 | |
| 1.18.0 | 6 / 0 | |
| 1.17.1 | 6 / 0 | |
| 1.17.0 | 6 / 0 | |
| 1.16.0 | 6 / 0 | |
| 1.15.0 | 6 / 0 | |
| 1.14.0 | 6 / 0 | |
| 1.13.0 | 6 / 0 |
v1.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.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.1
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.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.