c32check
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
ablanksteinzone117xhstovekyranjamieaulneaujcnelsonyknlreedrosenbluthblockstack-devops
Keywords
blockchainidauthauthenticationbitcoinblockchain authblockchain authenticationblockchainidblockchain idbitcoin authbitcoin authenticationbitcoin loginblockchain loginauthorizationloginsigninssocryptocryptographytokenblockstackblockstack authprofileidentityethereum
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is the core operation of this checksum library — converting hex strings to bytes for SHA256 hashing. This is legitimate cryptographic code, not payload obfuscation. | ai | |
| dependencies | unvetted-dep:cross-sha256 | AI (dependencies): cross-sha256 is a legitimate cross-platform SHA256 utility; appropriate for a library targeting both Node.js and browser environments. | ai |
v2.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.