@contrast/dep-hooks
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): jcolekaplan is an established Contrast Security publisher with clean track record; transition appears legitimate. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Contrast Security org internal maintainer rotation; same org publisher with clean track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Contrast Security org internal maintainer rotation; consistent with team changes, not a takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @contrast/core is same-org scoped dep; not a third-party supply chain risk. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Package is a module-hook library; Reflect.get on Module internals is its documented mechanism, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@contrast/core | AI (phantom-deps): Same-org scoped dep; declared in package.json as a runtime dependency, phantom-dep is a false positive here. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 1.35.0 | 5 / 0 | |
| 1.34.0 | 5 / 0 | |
| 1.33.0 | 5 / 0 | |
| 1.32.3 | 5 / 0 | |
| 1.32.2 | 5 / 0 | |
| 1.32.1 | 5 / 0 | |
| 1.32.0 | 5 / 0 | |
| 1.31.1 | 5 / 0 | |
| 1.31.0 | 5 / 0 | |
| 1.30.0 | 5 / 0 | |
| 1.29.1 | 5 / 0 | |
| 1.29.0 | 5 / 0 | |
| 1.28.1 | 5 / 0 | |
| 1.28.0 | 5 / 0 | |
| 1.27.0 | 5 / 0 | |
| 1.26.1 | 5 / 0 | |
| 1.26.0 | 4 / 0 | |
| 1.25.0 | 4 / 0 | |
| 1.24.0 | 4 / 0 | |
| 1.23.2 | 4 / 0 | |
| 1.23.1 | 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 | 4 / 0 | |
| 1.16.0 | 4 / 0 | |
| 1.15.0 | 4 / 0 | |
| 1.14.2 | 4 / 0 | |
| 1.14.1 | 4 / 0 | |
| 1.14.0 | 4 / 0 | |
| 1.13.0 | 4 / 0 | |
| 1.12.0 | 4 / 0 | |
| 1.11.0 | 4 / 0 | |
| 1.10.0 | 4 / 0 | |
| 1.9.0 | 4 / 0 | |
| 1.8.0 | 4 / 0 | |
| 1.7.0 | 4 / 0 | |
| 1.6.0 | 4 / 0 | |
| 1.5.0 | 3 / 0 |
v1.35.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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.