@keplr-wallet/stores-starknet
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): Keplr wallet migrated publishing to GitHub Actions CI with SLSA attestation; stable pattern for this org. | ai | |
| phantom-deps | phantom-dep:big-integer | AI (phantom-deps): Monorepo package; declared deps used transitively in build pipeline. | ai | |
| phantom-deps | phantom-dep:@ethersproject/abi | AI (phantom-deps): Monorepo package; ethersproject deps used transitively in build pipeline. | ai | |
| phantom-deps | phantom-dep:@ethersproject/bytes | AI (phantom-deps): Monorepo package; ethersproject deps used transitively in build pipeline. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decode is used for Starknet address validation (32-byte check), not payload hiding. | ai | |
| phantom-deps | phantom-dep:@ethersproject/address | AI (phantom-deps): Monorepo package; ethersproject deps used transitively in build pipeline. | ai | |
| phantom-deps | phantom-dep:@keplr-wallet/simple-fetch | AI (phantom-deps): Same-org monorepo package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ethersproject/transactions | AI (phantom-deps): Monorepo package; ethersproject deps used transitively in build pipeline. | ai | |
| phantom-deps | phantom-dep:@ethersproject/units | AI (phantom-deps): Monorepo package; ethersproject deps used transitively in build pipeline. | ai |
Versions (showing 15 of 115)
| Version | Deps | Published |
|---|---|---|
| 0.12.245 | 12 / 0 | |
| 0.12.244 | 12 / 0 | |
| 0.12.243 | 12 / 0 | |
| 0.12.242 | 12 / 0 | |
| 0.12.241 | 12 / 0 | |
| 0.12.240 | 12 / 0 | |
| 0.12.239 | 12 / 0 | |
| 0.12.238 | 12 / 0 | |
| 0.12.237 | 12 / 0 | |
| 0.12.236 | 12 / 0 | |
| 0.12.235 | 12 / 0 | |
| 0.12.234 | 12 / 0 | |
| 0.12.233 | 12 / 0 | |
| 0.12.232 | 12 / 0 | |
| 0.12.231 | 12 / 0 |
v0.12.245
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.244
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.243
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.242
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.241
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.240
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.239
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.238
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.237
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.236
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.235
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.234
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.233
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.232
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.231
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.