@keplr-wallet/stores-bitcoin
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 | publisher-changed | AI (provenance): Chainapsis migrated publishing to GitHub Actions CI/CD; SLSA attestation confirms official repo origin. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package from established publisher; missing metadata is expected pattern across all their packages. | ai | |
| phantom-deps | phantom-dep:@keplr-wallet/simple-fetch | AI (phantom-deps): Same-org sibling dependency; declared in package.json dependencies, stable false positive for this package. | ai |
Versions (showing 36 of 136)
| Version | Deps | Published |
|---|---|---|
| 0.12.248 | 7 / 0 | |
| 0.12.247 | 7 / 0 | |
| 0.12.246 | 7 / 0 | |
| 0.12.245 | 7 / 0 | |
| 0.12.244 | 7 / 0 | |
| 0.12.243 | 7 / 0 | |
| 0.12.242 | 7 / 0 | |
| 0.12.241 | 7 / 0 | |
| 0.12.240 | 7 / 0 | |
| 0.12.239 | 7 / 0 | |
| 0.12.238 | 7 / 0 | |
| 0.12.237 | 7 / 0 | |
| 0.12.236 | 7 / 0 | |
| 0.12.235 | 7 / 0 | |
| 0.12.234 | 7 / 0 | |
| 0.12.233 | 7 / 0 | |
| 0.12.232 | 7 / 0 | |
| 0.12.231 | 7 / 0 | |
| 0.12.230 | 7 / 0 | |
| 0.12.229 | 7 / 0 | |
| 0.12.228 | 7 / 0 | |
| 0.12.227 | 7 / 0 | |
| 0.12.226 | 7 / 0 | |
| 0.12.225 | 7 / 0 | |
| 0.12.224 | 7 / 0 | |
| 0.12.223 | 7 / 0 | |
| 0.12.222 | 7 / 0 | |
| 0.12.221 | 7 / 0 | |
| 0.12.220 | 7 / 0 | |
| 0.12.219 | 7 / 0 | |
| 0.12.218 | 7 / 0 | |
| 0.12.217 | 7 / 0 | |
| 0.12.216 | 7 / 0 | |
| 0.12.215 | 7 / 0 | |
| 0.12.214 | 7 / 0 | |
| 0.12.213 | 7 / 0 |
v0.12.230
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.229
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.228
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.227
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.226
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.225
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.224
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.223
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.222
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.221
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.220
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.219
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.218
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.217
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.216
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.215
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.214
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.213
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.