@keplr-wallet/crypto
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Provenance attestation is not yet standard practice; absence is not a security signal for established publishers. | ai | |
| dependencies | unvetted-dep:elliptic | AI (dependencies): elliptic is a standard, widely-used ECC library; its use is expected and appropriate for a crypto wallet utility package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established scoped package under @keplr-wallet with 1882 days history and 25k weekly downloads. Missing metadata fields are a hygiene issue, not a malice indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package; missing description is a cosmetic issue with no security relevance for this established package. | ai | |
| provenance | publisher-changed | AI (provenance): Chainapsis migrated publishing to GitHub Actions CI/CD with SLSA provenance attestation. This is a legitimate and recommended practice for the official keplr-wallet monorepo. | ai | |
| typosquat | typosquat.levenshtein:bcrypt | AI (typosquat): @keplr-wallet/crypto is a scoped crypto utility for the Keplr wallet SDK, not a typosquat of bcrypt. The name similarity is coincidental and the package has a long legitimate history. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decode usage in this package is exclusively in test vectors for cryptographic hash functions (hash.spec.ts). This is standard practice for crypto libraries and not a malicious payload indicator. | ai |
Versions (showing 67 of 367)
| Version | Deps | Published |
|---|---|---|
| 0.11.62 | 8 / 3 | |
| 0.11.61 | 8 / 3 | |
| 0.11.60 | 8 / 3 | |
| 0.11.59 | 8 / 3 | |
| 0.11.58 | 8 / 3 | |
| 0.11.57 | 8 / 3 | |
| 0.11.56 | 8 / 3 | |
| 0.11.53 | 8 / 3 | |
| 0.11.51 | 8 / 3 | |
| 0.11.50 | 8 / 3 | |
| 0.11.49 | 8 / 3 | |
| 0.11.48 | 8 / 3 | |
| 0.11.47 | 8 / 3 | |
| 0.11.46 | 8 / 3 | |
| 0.11.45 | 8 / 3 | |
| 0.11.44 | 8 / 3 | |
| 0.11.43 | 8 / 3 | |
| 0.11.42 | 8 / 3 | |
| 0.11.41 | 8 / 3 | |
| 0.11.34 | 8 / 3 | |
| 0.11.31 | 8 / 3 | |
| 0.11.25 | 8 / 3 | |
| 0.11.23 | 8 / 3 | |
| 0.11.21 | 8 / 3 | |
| 0.11.17 | 8 / 3 | |
| 0.11.16 | 8 / 3 | |
| 0.11.15 | 8 / 3 | |
| 0.11.13 | 8 / 3 | |
| 0.11.10 | 8 / 3 | |
| 0.11.9 | 7 / 3 | |
| 0.11.7 | 7 / 3 | |
| 0.11.4 | 7 / 3 | |
| 0.11.3 | 7 / 3 | |
| 0.11.2 | 7 / 3 | |
| 0.11.1 | 7 / 3 | |
| 0.11.0 | 7 / 3 | |
| 0.10.23 | 7 / 3 | |
| 0.10.22 | 7 / 3 | |
| 0.10.21 | 7 / 3 | |
| 0.10.19 | 7 / 3 | |
| 0.10.17 | 7 / 3 | |
| 0.10.16 | 7 / 3 | |
| 0.10.15 | 7 / 3 | |
| 0.10.14 | 7 / 3 | |
| 0.10.13 | 7 / 3 | |
| 0.10.12 | 7 / 3 | |
| 0.10.11 | 7 / 3 | |
| 0.10.10 | 7 / 3 | |
| 0.10.9 | 7 / 3 | |
| 0.10.8 | 7 / 3 | |
| 0.10.7 | 7 / 3 | |
| 0.10.5 | 7 / 3 | |
| 0.10.4 | 7 / 3 | |
| 0.10.3 | 7 / 3 | |
| 0.10.2 | 7 / 3 | |
| 0.10.0 | 6 / 3 | |
| 0.9.10 | 6 / 3 | |
| 0.9.9 | 6 / 4 | |
| 0.9.6 | 6 / 4 | |
| 0.9.5 | 6 / 4 | |
| 0.9.0 | 6 / 4 | |
| 0.8.8 | 6 / 5 | |
| 0.8.7 | 6 / 5 | |
| 0.8.6 | 6 / 5 | |
| 0.8.5 | 6 / 5 | |
| 0.8.4 | 6 / 5 | |
| 0.8.0 | 6 / 5 |
v0.11.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.