@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 — 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/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 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.40.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.