@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 47 of 151)
| Version | Deps | Published |
|---|---|---|
| 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 | |
| 1.16.1 | 24 / 4 | |
| 1.15.44 | 24 / 4 | |
| 1.15.43 | 24 / 4 | |
| 1.15.42 | 24 / 4 | |
| 1.15.41 | 24 / 4 | |
| 1.15.40 | 24 / 4 | |
| 1.15.39 | 24 / 4 | |
| 1.15.38 | 24 / 4 | |
| 1.15.37 | 24 / 4 | |
| 1.15.36 | 24 / 4 | |
| 1.15.35 | 24 / 4 | |
| 1.15.34 | 24 / 4 | |
| 1.15.33 | 24 / 4 | |
| 1.15.32 | 24 / 4 | |
| 1.15.31 | 24 / 4 | |
| 1.15.30 | 24 / 4 | |
| 1.15.29 | 24 / 4 | |
| 1.15.28 | 24 / 4 | |
| 1.15.27 | 24 / 4 | |
| 1.15.26 | 24 / 4 | |
| 1.15.25 | 24 / 4 | |
| 1.15.24 | 24 / 4 | |
| 1.15.23 | 24 / 4 | |
| 1.15.22 | 24 / 4 | |
| 1.15.21 | 24 / 4 | |
| 1.15.20 | 24 / 4 | |
| 1.15.19 | 24 / 4 | |
| 1.15.18 | 24 / 4 | |
| 1.15.17 | 24 / 4 | |
| 1.15.16 | 24 / 4 | |
| 1.15.15 | 24 / 4 | |
| 1.15.13 | 24 / 4 | |
| 1.15.12 | 24 / 4 | |
| 1.15.9 | 24 / 4 | |
| 1.15.6 | 23 / 4 | |
| 1.15.5 | 23 / 4 | |
| 1.15.4 | 23 / 4 | |
| 1.15.3 | 23 / 4 |
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.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.13
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.9
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.