@qnx/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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:https://github.com/yatendra121 | AI (email-domain): Author field contains a GitHub profile URL, not an email address; no real domain hijack risk. | ai | |
| typosquat | typosquat.levenshtein:bcrypt | AI (typosquat): Scoped @qnx/crypto package in a monorepo; not impersonating bcrypt. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.8.7 | 0 / 0 | |
| 0.8.0 | 0 / 16 | |
| 0.7.13 | 0 / 16 | |
| 0.7.12 | 0 / 16 | |
| 0.7.10 | 0 / 16 | |
| 0.7.9 | 0 / 16 | |
| 0.7.8 | 0 / 16 |
v0.8.7
2 findingsMaintainer email 'https://github.com/yatendra121' uses domain 'https://github.com/yatendra121' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
2 findingsMaintainer email 'https://github.com/yatendra121' uses domain 'https://github.com/yatendra121' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.13
2 findingsMaintainer email 'https://github.com/yatendra121' uses domain 'https://github.com/yatendra121' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.12
2 findingsMaintainer email 'https://github.com/yatendra121' uses domain 'https://github.com/yatendra121' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.10
2 findingsMaintainer email 'https://github.com/yatendra121' uses domain 'https://github.com/yatendra121' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.9
2 findingsMaintainer email 'https://github.com/yatendra121' uses domain 'https://github.com/yatendra121' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.8
2 findingsMaintainer email 'https://github.com/yatendra121' uses domain 'https://github.com/yatendra121' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.