@keplr-wallet/stores-eth
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Consistent with monorepo sub-package pattern from chainapsis; not a spam indicator here. | ai | |
| phantom-deps | phantom-dep:@keplr-wallet/simple-fetch | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing description/repo/keywords is normal for internal scoped packages. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex encoding used for Ethereum transaction serialization; standard pattern in this wallet package. | ai |
Versions (showing 26 of 226)
| Version | Deps | Published |
|---|---|---|
| 0.12.113 | 12 / 0 | |
| 0.12.112 | 12 / 0 | |
| 0.12.111 | 12 / 0 | |
| 0.12.110 | 12 / 0 | |
| 0.12.109 | 12 / 0 | |
| 0.12.108 | 12 / 0 | |
| 0.12.107 | 12 / 0 | |
| 0.12.106 | 12 / 0 | |
| 0.12.105 | 12 / 0 | |
| 0.12.104 | 12 / 0 | |
| 0.12.103 | 12 / 0 | |
| 0.12.102 | 12 / 0 | |
| 0.12.101 | 12 / 0 | |
| 0.12.100 | 12 / 0 | |
| 0.12.98 | 12 / 0 | |
| 0.12.96 | 12 / 0 | |
| 0.12.95 | 12 / 0 | |
| 0.12.94 | 12 / 0 | |
| 0.12.91 | 12 / 0 | |
| 0.12.90 | 12 / 0 | |
| 0.12.89 | 12 / 0 | |
| 0.12.88 | 12 / 0 | |
| 0.12.87 | 12 / 0 | |
| 0.12.86 | 14 / 0 | |
| 0.12.85 | 14 / 0 | |
| 0.12.84 | 14 / 0 |
v0.12.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.