@injectivelabs/wallet-cosmostation
Cosmostation strategy for use with @injectivelabs/wallet-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@cosmostation/cosmos-client | AI (dependencies): Official Cosmostation client library; expected dependency for a Cosmostation wallet strategy package. | ai | |
| provenance | no-provenance | AI (provenance): Large InjectiveLabs monorepo; no provenance is consistent across all their packages. | ai | |
| phantom-deps | phantom-dep:@injectivelabs/utils | AI (phantom-deps): Same-org package; likely used transitively or via re-exports within the monorepo. | ai | |
| phantom-deps | phantom-dep:@walletconnect/ethereum-provider | AI (phantom-deps): Referenced in config files per the finding; stable false positive for this wallet integration package. | ai |
Versions (showing 71 of 171)
| Version | Deps | Published |
|---|---|---|
| 1.16.7 | 8 / 0 | |
| 1.16.6 | 8 / 0 | |
| 1.16.5 | 8 / 0 | |
| 1.16.4 | 8 / 0 | |
| 1.16.3 | 8 / 0 | |
| 1.16.2 | 8 / 0 | |
| 1.16.1 | 8 / 0 | |
| 1.15.43 | 8 / 0 | |
| 1.15.42 | 8 / 0 | |
| 1.15.41 | 8 / 0 | |
| 1.15.40 | 8 / 0 | |
| 1.15.39 | 8 / 0 | |
| 1.15.38 | 8 / 0 | |
| 1.15.37 | 8 / 0 | |
| 1.15.36 | 8 / 0 | |
| 1.15.35 | 8 / 0 | |
| 1.15.34 | 8 / 0 | |
| 1.15.33 | 8 / 0 | |
| 1.15.32 | 8 / 0 | |
| 1.15.31 | 8 / 0 | |
| 1.15.30 | 8 / 0 | |
| 1.15.29 | 8 / 0 | |
| 1.15.28 | 8 / 0 | |
| 1.15.27 | 8 / 0 | |
| 1.15.26 | 8 / 0 | |
| 1.15.25 | 8 / 0 | |
| 1.15.24 | 8 / 0 | |
| 1.15.23 | 8 / 0 | |
| 1.15.22 | 8 / 0 | |
| 1.15.21 | 8 / 0 | |
| 1.15.20 | 8 / 0 | |
| 1.15.19 | 8 / 0 | |
| 1.15.18 | 8 / 0 | |
| 1.15.17 | 8 / 0 | |
| 1.15.16 | 8 / 0 | |
| 1.15.15 | 8 / 0 | |
| 1.15.14 | 8 / 0 | |
| 1.15.12 | 8 / 0 | |
| 1.15.11 | 8 / 0 | |
| 1.15.10 | 8 / 0 | |
| 1.15.9 | 8 / 0 | |
| 1.15.8 | 8 / 0 | |
| 1.15.7 | 8 / 0 | |
| 1.15.6 | 8 / 0 | |
| 1.15.5 | 8 / 0 | |
| 1.15.4 | 8 / 0 | |
| 1.15.3 | 8 / 0 | |
| 1.15.2 | 8 / 0 | |
| 1.15.1 | 8 / 0 | |
| 1.14.57 | 8 / 0 | |
| 1.14.56 | 8 / 0 | |
| 1.14.55 | 8 / 0 | |
| 1.14.54 | 8 / 0 | |
| 1.14.53 | 8 / 0 | |
| 1.14.52 | 8 / 0 | |
| 1.14.51 | 8 / 0 | |
| 1.14.50 | 8 / 0 | |
| 1.14.49 | 8 / 0 | |
| 1.14.48 | 8 / 0 | |
| 1.14.47 | 8 / 0 | |
| 1.14.46 | 8 / 0 | |
| 1.14.45 | 8 / 0 | |
| 1.14.44 | 8 / 0 | |
| 1.14.43 | 8 / 0 | |
| 1.14.41 | 8 / 0 | |
| 1.14.40 | 8 / 0 | |
| 1.14.35 | 8 / 0 | |
| 1.14.33 | 8 / 0 | |
| 1.14.32 | 8 / 0 | |
| 1.14.31 | 8 / 0 | |
| 1.14.30 | 8 / 0 |
v1.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.