@injectivelabs/wallet-private-key
Private key wallet 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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Pipeline migrated to GitHub Actions with SLSA attestation; gitHead absence is expected in this CI setup. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher is a legitimate automation change for this org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal consistent with org-level CI migration; no malware indicators present. | ai | |
| dependencies | unvetted-dep:@injectivelabs/sdk-ts | AI (dependencies): Same-org monorepo sibling dependency; expected for this package family. | ai | |
| dependencies | unvetted-dep:@injectivelabs/wallet-base | AI (dependencies): Same-org monorepo sibling dependency; expected for this package family. | ai |
Versions (showing 89 of 189)
| Version | Deps | Published |
|---|---|---|
| 1.16.25 | 4 / 1 | |
| 1.16.24 | 4 / 1 | |
| 1.16.23 | 4 / 1 | |
| 1.16.22 | 4 / 1 | |
| 1.16.21 | 4 / 1 | |
| 1.16.20 | 4 / 1 | |
| 1.16.19 | 4 / 1 | |
| 1.16.18 | 4 / 1 | |
| 1.16.17 | 4 / 1 | |
| 1.16.16 | 4 / 1 | |
| 1.16.15 | 4 / 1 | |
| 1.16.14 | 4 / 1 | |
| 1.16.13 | 4 / 1 | |
| 1.16.12 | 4 / 1 | |
| 1.16.11 | 4 / 1 | |
| 1.16.10 | 4 / 1 | |
| 1.16.9 | 4 / 1 | |
| 1.16.8 | 4 / 1 | |
| 1.16.7 | 4 / 0 | |
| 1.16.6 | 4 / 0 | |
| 1.16.5 | 4 / 0 | |
| 1.16.4 | 4 / 0 | |
| 1.16.3 | 4 / 0 | |
| 1.16.2 | 4 / 0 | |
| 1.16.1 | 4 / 0 | |
| 1.15.43 | 4 / 0 | |
| 1.15.42 | 4 / 0 | |
| 1.15.41 | 4 / 0 | |
| 1.15.40 | 4 / 0 | |
| 1.15.39 | 4 / 0 | |
| 1.15.38 | 4 / 0 | |
| 1.15.37 | 4 / 0 | |
| 1.15.36 | 4 / 0 | |
| 1.15.35 | 4 / 0 | |
| 1.15.34 | 4 / 0 | |
| 1.15.33 | 4 / 0 | |
| 1.15.32 | 4 / 0 | |
| 1.15.31 | 4 / 0 | |
| 1.15.30 | 4 / 0 | |
| 1.15.29 | 4 / 0 | |
| 1.15.28 | 4 / 0 | |
| 1.15.27 | 4 / 0 | |
| 1.15.26 | 4 / 0 | |
| 1.15.25 | 4 / 0 | |
| 1.15.24 | 4 / 0 | |
| 1.15.23 | 4 / 0 | |
| 1.15.22 | 4 / 0 | |
| 1.15.21 | 4 / 0 | |
| 1.15.20 | 4 / 0 | |
| 1.15.19 | 4 / 0 | |
| 1.15.18 | 4 / 0 | |
| 1.15.17 | 4 / 0 | |
| 1.15.16 | 4 / 0 | |
| 1.15.15 | 4 / 0 | |
| 1.15.14 | 4 / 0 | |
| 1.15.12 | 4 / 0 | |
| 1.15.11 | 4 / 0 | |
| 1.15.10 | 4 / 0 | |
| 1.15.9 | 4 / 0 | |
| 1.15.8 | 4 / 0 | |
| 1.15.7 | 4 / 0 | |
| 1.15.6 | 4 / 0 | |
| 1.15.5 | 4 / 0 | |
| 1.15.4 | 4 / 0 | |
| 1.15.3 | 4 / 0 | |
| 1.15.2 | 4 / 0 | |
| 1.15.1 | 4 / 0 | |
| 1.14.57 | 4 / 0 | |
| 1.14.56 | 4 / 0 | |
| 1.14.55 | 4 / 0 | |
| 1.14.54 | 4 / 0 | |
| 1.14.53 | 4 / 0 | |
| 1.14.52 | 4 / 0 | |
| 1.14.51 | 4 / 0 | |
| 1.14.50 | 4 / 0 | |
| 1.14.49 | 4 / 0 | |
| 1.14.48 | 4 / 0 | |
| 1.14.47 | 4 / 0 | |
| 1.14.46 | 4 / 0 | |
| 1.14.45 | 4 / 0 | |
| 1.14.44 | 4 / 0 | |
| 1.14.43 | 4 / 0 | |
| 1.14.41 | 5 / 0 | |
| 1.14.40 | 5 / 0 | |
| 1.14.35 | 5 / 0 | |
| 1.14.33 | 5 / 0 | |
| 1.14.32 | 5 / 0 | |
| 1.14.31 | 5 / 0 | |
| 1.14.30 | 5 / 0 |
v1.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.