jshashes
1
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
h2non
Keywords
hashmd5sha1sha256hashessha512RIPEMDbase64hmaccrcencodingalgorithm
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:rijndael-project.com | AI (email-domain): Domain belongs to a contributor entry, not the active publisher; package is 13+ years old with no abuse history. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.0.8 | 0 / 2 |
v1.0.8
2 findings
HIGH
Unclaimed maintainer email domain: rijndael-project.com
email-domain
Maintainer email '[email protected]' uses domain 'rijndael-project.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
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.