@injectivelabs/wallet-base
Base 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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation confirms CI/CD publish; dormancy explained by active monorepo release cadence, not account takeover indicators. | ai | |
| dependencies | unvetted-dep:@injectivelabs/sdk-ts | AI (dependencies): First-party sibling package from InjectiveLabs monorepo; expected dependency for this wallet library. | ai | |
| dependencies | unvetted-dep:eip1193-provider | AI (dependencies): Standard EIP-1193 provider interface package; appropriate dependency for a wallet base library. | ai |
Versions (showing 25 of 130)
| Version | Deps | Published |
|---|---|---|
| 1.15.28 | 5 / 1 | |
| 1.15.27 | 5 / 1 | |
| 1.15.26 | 5 / 1 | |
| 1.15.25 | 5 / 1 | |
| 1.15.24 | 5 / 1 | |
| 1.15.23 | 5 / 1 | |
| 1.15.22 | 5 / 1 | |
| 1.15.21 | 5 / 1 | |
| 1.15.20 | 5 / 1 | |
| 1.15.19 | 5 / 1 | |
| 1.15.18 | 5 / 1 | |
| 1.15.17 | 5 / 1 | |
| 1.15.16 | 5 / 1 | |
| 1.15.15 | 5 / 1 | |
| 1.15.14 | 5 / 1 | |
| 1.15.12 | 5 / 1 | |
| 1.15.11 | 5 / 1 | |
| 1.15.10 | 5 / 1 | |
| 1.15.9 | 5 / 1 | |
| 1.15.8 | 5 / 1 | |
| 1.15.7 | 5 / 1 | |
| 1.15.6 | 5 / 1 | |
| 1.15.5 | 5 / 1 | |
| 1.15.4 | 5 / 1 | |
| 1.15.3 | 5 / 1 |
v1.15.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.