@contrast/esm-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 13 approved packages; transition appears legitimate. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Enterprise security vendor package; sparse public metadata is expected for internal tooling components. | ai |
Versions (showing 58 of 58)
| Version | Deps | Published |
|---|---|---|
| 2.41.0 | 6 / 0 | |
| 2.40.0 | 6 / 0 | |
| 2.39.0 | 6 / 0 | |
| 2.38.5 | 6 / 0 | |
| 2.38.4 | 6 / 0 | |
| 2.38.3 | 6 / 0 | |
| 2.38.2 | 6 / 0 | |
| 2.38.1 | 6 / 0 | |
| 2.38.0 | 6 / 0 | |
| 2.37.1 | 6 / 0 | |
| 2.37.0 | 6 / 0 | |
| 2.36.0 | 6 / 0 | |
| 2.35.2 | 6 / 0 | |
| 2.35.1 | 6 / 0 | |
| 2.35.0 | 6 / 0 | |
| 2.34.1 | 6 / 0 | |
| 2.34.0 | 6 / 0 | |
| 2.33.0 | 6 / 0 | |
| 2.32.0 | 6 / 0 | |
| 2.31.0 | 6 / 0 | |
| 2.30.0 | 6 / 0 | |
| 2.29.0 | 6 / 0 | |
| 2.28.2 | 6 / 0 | |
| 2.28.1 | 6 / 0 | |
| 2.28.0 | 6 / 0 | |
| 2.27.0 | 6 / 0 | |
| 2.26.0 | 6 / 0 | |
| 2.25.0 | 6 / 0 | |
| 2.24.0 | 6 / 0 | |
| 2.23.0 | 6 / 0 | |
| 2.22.0 | 6 / 0 | |
| 2.21.0 | 6 / 0 | |
| 2.20.0 | 6 / 0 | |
| 2.19.4 | 6 / 0 | |
| 2.19.3 | 6 / 0 | |
| 2.19.2 | 6 / 0 | |
| 2.19.1 | 6 / 0 | |
| 2.19.0 | 6 / 0 | |
| 2.18.0 | 6 / 0 | |
| 2.17.0 | 6 / 0 | |
| 2.16.0 | 6 / 0 | |
| 2.15.1 | 6 / 0 | |
| 2.15.0 | 6 / 0 | |
| 2.14.0 | 6 / 0 | |
| 2.13.0 | 6 / 0 | |
| 2.12.0 | 6 / 0 | |
| 2.11.0 | 6 / 0 | |
| 2.10.0 | 6 / 0 | |
| 2.9.1 | 6 / 0 | |
| 2.9.0 | 3 / 0 | |
| 2.8.1 | 3 / 0 | |
| 2.8.0 | 3 / 0 | |
| 2.7.0 | 3 / 0 | |
| 2.6.3 | 3 / 0 | |
| 2.6.2 | 3 / 0 | |
| 2.6.1 | 3 / 0 | |
| 2.6.0 | 3 / 0 | |
| 2.5.2 | 3 / 0 |
v2.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.