@keplr-wallet/stores-core
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): Transition from chainapsis user to GitHub Actions CI/CD is consistent with SLSA-attested automated publishing from the official repo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Part of a large monorepo (629 versions); dormancy reflects release cadence, not takeover. SLSA attestation confirms legitimate CI origin. | ai | |
| provenance | no-provenance | AI (provenance): Publisher has never used provenance attestation across 3520 approved packages; consistent pattern. | ai | |
| dependencies | unvetted-dep:@keplr-wallet/stores | AI (dependencies): Sibling monorepo package from same publisher; pinned to matching version. | ai | |
| dependencies | unvetted-dep:@keplr-wallet/background | AI (dependencies): Sibling monorepo package from same publisher; pinned to matching version. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo package from established publisher; missing metadata is a known pattern for internal workspace packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Keplr-wallet monorepo packages consistently omit descriptions; stable false positive for this package. | ai |
Versions (showing 15 of 115)
| Version | Deps | Published |
|---|---|---|
| 0.12.245 | 8 / 0 | |
| 0.12.244 | 8 / 0 | |
| 0.12.243 | 8 / 0 | |
| 0.12.242 | 8 / 0 | |
| 0.12.241 | 8 / 0 | |
| 0.12.240 | 8 / 0 | |
| 0.12.239 | 8 / 0 | |
| 0.12.238 | 8 / 0 | |
| 0.12.237 | 8 / 0 | |
| 0.12.236 | 8 / 0 | |
| 0.12.235 | 8 / 0 | |
| 0.12.234 | 8 / 0 | |
| 0.12.233 | 8 / 0 | |
| 0.12.232 | 8 / 0 | |
| 0.12.231 | 8 / 0 |
v0.12.245
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.244
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.243
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.242
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.241
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.240
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.239
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.238
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.237
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.236
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.12.235
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.12.234
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.12.233
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.12.232
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.12.231
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.