@injectivelabs/wallet-strategy
Wallet strategy with instantiated wallets
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@ethereumjs/tx | AI (phantom-deps): Monorepo peer-dep pattern; declared for type resolution, not direct import. | ai | |
| phantom-deps | phantom-dep:ethereumjs-util | AI (phantom-deps): Monorepo peer-dep pattern; declared for type resolution, not direct import. | ai | |
| phantom-deps | phantom-dep:@injectivelabs/exceptions | AI (phantom-deps): Same org scope; monorepo transitive dep pattern, stable across versions. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/common | AI (phantom-deps): Monorepo peer-dep pattern; declared for type resolution, not direct import. | ai | |
| phantom-deps | phantom-dep:eth-sig-util | AI (phantom-deps): Monorepo peer-dep pattern; declared for type resolution, not direct import. | ai | |
| phantom-deps | phantom-dep:eip1193-provider | AI (phantom-deps): Monorepo pattern; declared at strategy level, consumed by sub-packages. | ai | |
| phantom-deps | phantom-dep:@injectivelabs/sdk-ts | AI (phantom-deps): Same-org monorepo dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@injectivelabs/networks | AI (phantom-deps): Same-org monorepo dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@injectivelabs/ts-types | AI (phantom-deps): Same-org monorepo dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@injectivelabs/utils | AI (phantom-deps): Same-org monorepo dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:viem | AI (phantom-deps): Monorepo pattern; declared at strategy level, consumed by sub-packages. | ai | |
| phantom-deps | phantom-dep:hdkey | AI (phantom-deps): Monorepo pattern; declared at strategy level, consumed by sub-packages. | ai | |
| phantom-deps | phantom-dep:ethers | AI (phantom-deps): Monorepo pattern; declared at strategy level, consumed by sub-packages. | ai | |
| phantom-deps | phantom-dep:alchemy-sdk | AI (phantom-deps): Monorepo pattern; declared at strategy level, consumed by sub-packages. | ai | |
| dependencies | unvetted-dep:@injectivelabs/wallet-magic | AI (dependencies): Same-org monorepo sibling at matching version; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@injectivelabs/wallet-wallet-connect | AI (dependencies): Same-org monorepo sibling at matching version; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@injectivelabs/wallet-turnkey | AI (dependencies): Same-org monorepo sibling at matching version; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@injectivelabs/wallet-trezor | AI (dependencies): Same-org monorepo sibling at matching version; not a third-party risk. | ai |
Versions (showing 100 of 138)
| Version | Deps | Published |
|---|---|---|
| 1.20.1 | 11 / 0 | |
| 1.19.29 | 11 / 0 | |
| 1.19.28 | 11 / 0 | |
| 1.19.27 | 11 / 0 | |
| 1.19.26 | 11 / 0 | |
| 1.19.25 | 11 / 0 | |
| 1.19.24 | 11 / 0 | |
| 1.19.23 | 11 / 0 | |
| 1.19.22 | 11 / 0 | |
| 1.19.21 | 11 / 0 | |
| 1.19.20 | 11 / 0 | |
| 1.19.19 | 11 / 0 | |
| 1.19.18 | 11 / 0 | |
| 1.19.17 | 11 / 0 | |
| 1.19.16 | 11 / 0 | |
| 1.19.15 | 11 / 0 | |
| 1.19.14 | 11 / 0 | |
| 1.19.13 | 11 / 0 | |
| 1.19.12 | 11 / 0 | |
| 1.19.11 | 11 / 0 | |
| 1.19.10 | 11 / 0 | |
| 1.19.9 | 11 / 0 | |
| 1.19.8 | 11 / 0 | |
| 1.19.7 | 11 / 0 | |
| 1.19.6 | 11 / 0 | |
| 1.19.5 | 11 / 0 | |
| 1.19.4 | 11 / 0 | |
| 1.19.3 | 11 / 0 | |
| 1.19.2 | 11 / 0 | |
| 1.19.1 | 11 / 0 | |
| 1.19.0 | 11 / 0 | |
| 1.18.24 | 11 / 0 | |
| 1.18.23 | 11 / 0 | |
| 1.18.22 | 11 / 0 | |
| 1.18.21 | 11 / 0 | |
| 1.18.20 | 11 / 0 | |
| 1.18.19 | 11 / 0 | |
| 1.18.18 | 11 / 0 | |
| 1.18.17 | 11 / 0 | |
| 1.18.16 | 11 / 0 | |
| 1.18.15 | 11 / 0 | |
| 1.18.14 | 11 / 0 | |
| 1.18.13 | 11 / 0 | |
| 1.18.12 | 11 / 0 | |
| 1.18.11 | 11 / 0 | |
| 1.18.10 | 11 / 0 | |
| 1.18.9 | 11 / 0 | |
| 1.18.8 | 11 / 0 | |
| 1.18.7 | 11 / 0 | |
| 1.18.6 | 11 / 0 | |
| 1.18.5 | 11 / 0 | |
| 1.18.4 | 11 / 0 | |
| 1.18.3 | 11 / 0 | |
| 1.18.2 | 11 / 0 | |
| 1.18.1 | 11 / 0 | |
| 1.17.9 | 11 / 0 | |
| 1.17.8 | 11 / 0 | |
| 1.17.7 | 11 / 0 | |
| 1.17.6 | 11 / 0 | |
| 1.17.5 | 11 / 0 | |
| 1.17.4 | 11 / 0 | |
| 1.17.3 | 11 / 0 | |
| 1.17.2 | 11 / 0 | |
| 1.16.38 | 21 / 2 | |
| 1.16.37 | 21 / 2 | |
| 1.16.36 | 21 / 2 | |
| 1.16.35 | 21 / 2 | |
| 1.16.34 | 21 / 2 | |
| 1.16.33 | 21 / 2 | |
| 1.16.32 | 21 / 2 | |
| 1.16.31 | 21 / 2 | |
| 1.16.30 | 21 / 2 | |
| 1.16.29 | 21 / 2 | |
| 1.16.28 | 21 / 2 | |
| 1.16.27 | 21 / 2 | |
| 1.16.26 | 21 / 2 | |
| 1.16.25 | 21 / 2 | |
| 1.16.24 | 21 / 2 | |
| 1.16.23 | 21 / 2 | |
| 1.16.22 | 21 / 2 | |
| 1.16.21 | 21 / 2 | |
| 1.16.20 | 21 / 2 | |
| 1.16.19 | 21 / 2 | |
| 1.16.18 | 21 / 2 | |
| 1.16.17 | 21 / 2 | |
| 1.16.16 | 21 / 2 | |
| 1.16.15 | 21 / 2 | |
| 1.16.14 | 21 / 2 | |
| 1.16.13 | 21 / 2 | |
| 1.16.12 | 24 / 4 | |
| 1.16.11 | 24 / 4 | |
| 1.16.10 | 24 / 4 | |
| 1.16.9 | 24 / 4 | |
| 1.16.8 | 24 / 4 | |
| 1.16.7 | 24 / 4 | |
| 1.16.6 | 24 / 4 | |
| 1.16.5 | 24 / 4 | |
| 1.16.4 | 24 / 4 | |
| 1.16.3 | 24 / 4 | |
| 1.16.2 | 24 / 4 |
v1.20.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.16.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.