@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 60 of 260)
| Version | Deps | Published |
|---|---|---|
| 0.12.148 | 8 / 0 | |
| 0.12.147 | 8 / 0 | |
| 0.12.146 | 8 / 0 | |
| 0.12.145 | 8 / 0 | |
| 0.12.144 | 8 / 0 | |
| 0.12.143 | 8 / 0 | |
| 0.12.142 | 8 / 0 | |
| 0.12.141 | 8 / 0 | |
| 0.12.140 | 8 / 0 | |
| 0.12.139 | 8 / 0 | |
| 0.12.138 | 8 / 0 | |
| 0.12.137 | 8 / 0 | |
| 0.12.136 | 8 / 0 | |
| 0.12.135 | 8 / 0 | |
| 0.12.133 | 8 / 0 | |
| 0.12.132 | 8 / 0 | |
| 0.12.131 | 8 / 0 | |
| 0.12.130 | 8 / 0 | |
| 0.12.129 | 8 / 0 | |
| 0.12.128 | 8 / 0 | |
| 0.12.127 | 8 / 0 | |
| 0.12.126 | 8 / 0 | |
| 0.12.125 | 8 / 0 | |
| 0.12.124 | 8 / 0 | |
| 0.12.123 | 8 / 0 | |
| 0.12.122 | 8 / 0 | |
| 0.12.121 | 8 / 0 | |
| 0.12.120 | 8 / 0 | |
| 0.12.119 | 8 / 0 | |
| 0.12.118 | 8 / 0 | |
| 0.12.117 | 8 / 0 | |
| 0.12.116 | 8 / 0 | |
| 0.12.115 | 8 / 0 | |
| 0.12.114 | 8 / 0 | |
| 0.12.113 | 8 / 0 | |
| 0.12.112 | 8 / 0 | |
| 0.12.111 | 8 / 0 | |
| 0.12.110 | 8 / 0 | |
| 0.12.109 | 8 / 0 | |
| 0.12.108 | 8 / 0 | |
| 0.12.107 | 8 / 0 | |
| 0.12.106 | 8 / 0 | |
| 0.12.105 | 8 / 0 | |
| 0.12.104 | 8 / 0 | |
| 0.12.103 | 8 / 0 | |
| 0.12.102 | 8 / 0 | |
| 0.12.101 | 8 / 0 | |
| 0.12.100 | 8 / 0 | |
| 0.12.98 | 8 / 0 | |
| 0.12.96 | 8 / 0 | |
| 0.12.95 | 8 / 0 | |
| 0.12.94 | 8 / 0 | |
| 0.12.91 | 8 / 0 | |
| 0.12.90 | 8 / 0 | |
| 0.12.89 | 8 / 0 | |
| 0.12.88 | 8 / 0 | |
| 0.12.87 | 8 / 0 | |
| 0.12.86 | 10 / 0 | |
| 0.12.85 | 10 / 0 | |
| 0.12.84 | 10 / 0 |
v0.12.148
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.147
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.146
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.145
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.144
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.143
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.142
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.141
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.140
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.139
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.138
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.137
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.136
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.135
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.133
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.132
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.131
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.130
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.129
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.128
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.127
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.126
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.125
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.124
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.123
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.122
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.121
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.120
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.119
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.118
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.117
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.116
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.115
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.114
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.113
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.112
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.111
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.110
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.109
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.108
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.107
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.106
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.105
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.104
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.103
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.102
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.101
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.100
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.98
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.96
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.95
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.94
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.91
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.90
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.89
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.88
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.87
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.86
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.85
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.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.