@iov/crypto
Cryptography resources for IOV projects
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): Publisher change from albert.andrejev to iovdave occurred in Feb 2020; iovdave has since published 148 approved packages with 0 rejections — clearly a legitimate org transition. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): ripemd160 is a well-known, legitimate cryptographic hashing package; its addition to a crypto library is expected and benign. | ai | |
| dependencies | unvetted-dep:elliptic | AI (dependencies): elliptic is a standard, widely-used EC cryptography library; its use in a crypto package is expected and appropriate across all versions. | ai | |
| dependencies | unvetted-dep:type-tagger | AI (dependencies): type-tagger is a lightweight TypeScript type-tagging utility; low risk and consistent across versions of this package. | ai | |
| email-domain | unclaimed-email:iov.one | AI (email-domain): iov.one is the established domain for IOV SAS, a known organization with 125 approved packages and 7+ years of history. Latent domain-hijack risk does not outweigh the package's established legitimacy. | ai |
Versions (showing 60 of 60)
| Version | Deps | Published |
|---|---|---|
| 2.5.0 | 1 / 0 | |
| 2.3.2 | 11 / 7 | |
| 2.2.0 | 11 / 2 | |
| 2.1.0 | 11 / 2 | |
| 2.0.2 | 11 / 1 | |
| 2.0.1 | 11 / 1 | |
| 1.1.0 | 10 / 1 | |
| 1.0.0 | 10 / 1 | |
| 0.17.8 | 10 / 1 | |
| 0.17.7 | 10 / 1 | |
| 0.17.6 | 10 / 1 | |
| 0.17.5 | 10 / 1 | |
| 0.17.4 | 10 / 1 | |
| 0.17.3 | 10 / 1 | |
| 0.17.2 | 10 / 1 | |
| 0.17.1 | 10 / 1 | |
| 0.17.0 | 10 / 1 | |
| 0.16.3 | 10 / 1 | |
| 0.16.2 | 10 / 1 | |
| 0.16.1 | 10 / 1 | |
| 0.16.0 | 10 / 1 | |
| 0.15.0 | 10 / 1 | |
| 0.14.5 | 10 / 1 | |
| 0.14.4 | 10 / 1 | |
| 0.14.3 | 10 / 1 | |
| 0.14.2 | 10 / 1 | |
| 0.14.1 | 10 / 1 | |
| 0.14.0 | 10 / 1 | |
| 0.13.8 | 10 / 1 | |
| 0.13.7 | 10 / 1 | |
| 0.13.6 | 10 / 1 | |
| 0.13.5 | 10 / 1 | |
| 0.13.4 | 10 / 1 | |
| 0.13.3 | 10 / 1 | |
| 0.13.2 | 10 / 1 | |
| 0.13.1 | 10 / 1 | |
| 0.13.0 | 10 / 1 | |
| 0.12.3 | 10 / 1 | |
| 0.12.2 | 10 / 1 | |
| 0.12.1 | 10 / 1 | |
| 0.12.0 | 10 / 1 | |
| 0.11.0 | 10 / 1 | |
| 0.10.4 | 11 / 1 | |
| 0.10.1 | 11 / 1 | |
| 0.10.0 | 11 / 1 | |
| 0.9.1 | 11 / 1 | |
| 0.9.0 | 11 / 1 | |
| 0.8.1 | 11 / 1 | |
| 0.8.0 | 10 / 1 | |
| 0.7.1 | 10 / 1 | |
| 0.7.0 | 10 / 1 | |
| 0.6.1 | 10 / 1 | |
| 0.6.0 | 10 / 1 | |
| 0.5.3 | 9 / 1 | |
| 0.5.2 | 9 / 1 | |
| 0.5.0 | 9 / 1 | |
| 0.4.0 | 9 / 1 | |
| 0.3.1 | 9 / 1 | |
| 0.3.0 | 9 / 1 | |
| 0.2.0 | 9 / 1 |
v2.5.0
2 findingsMaintainer email '[email protected]' uses domain 'iov.one' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsMaintainer email '[email protected]' uses domain 'iov.one' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
2 findingsThis version was published by a different npm account than previous versions on 2020-02-14. 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.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.