@enbox/crypto
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:bcrypt | AI (typosquat): Scoped @enbox/crypto package with legitimate org, repo, and contributors; not a bcrypt typosquat. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.1.8 | 5 / 11 | |
| 0.1.7 | 5 / 11 | |
| 0.1.6 | 5 / 11 | |
| 0.1.5 | 5 / 11 | |
| 0.1.4 | 5 / 9 | |
| 0.1.3 | 5 / 9 | |
| 0.1.2 | 5 / 9 | |
| 0.1.1 | 5 / 9 | |
| 0.1.0 | 5 / 9 | |
| 0.0.8 | 5 / 10 | |
| 0.0.7 | 5 / 9 | |
| 0.0.6 | 5 / 9 | |
| 0.0.5 | 5 / 9 | |
| 0.0.4 | 4 / 9 | |
| 0.0.3 | 4 / 12 | |
| 0.0.2 | 4 / 24 | |
| 0.0.1 | 4 / 24 |
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.