@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 — 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 |
|---|---|---|---|---|
| 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 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.32.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.2
2 findingsThis version was published by a different npm account than previous versions on 2026-04-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-31. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.1
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.