@crypticdot/defituna-client
Typescript client to interact with DefiTuna's on-chain program.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@crypticdot/pump-amm-solana-client | AI (phantom-deps): Same-org dep likely re-exported or used transitively. | ai | |
| phantom-deps | phantom-dep:@crypticdot/defituna-core | AI (phantom-deps): Same-org monorepo package; phantom-dep heuristic fires on re-exported or indirect usage patterns. | ai | |
| phantom-deps | phantom-dep:@crypticdot/fusionamm-sdk | AI (phantom-deps): Same-org package; likely re-exported or used indirectly through other fusionamm deps. | ai | |
| phantom-deps | phantom-dep:@orca-so/whirlpools | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@solana-program/compute-budget | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai |
Versions (showing 51 of 89)
| Version | Deps | Published |
|---|---|---|
| 3.7.2 | 17 / 21 | |
| 3.7.1 | 17 / 21 | |
| 3.7.0 | 17 / 21 | |
| 3.6.25 | 17 / 21 | |
| 3.6.23 | 17 / 21 | |
| 3.6.22 | 17 / 21 | |
| 3.6.21 | 17 / 21 | |
| 3.6.20 | 17 / 21 | |
| 3.6.19 | 16 / 21 | |
| 3.6.18 | 16 / 21 | |
| 3.6.17 | 16 / 21 | |
| 3.6.16 | 16 / 21 | |
| 3.6.14 | 16 / 21 | |
| 3.6.13 | 16 / 21 | |
| 3.6.12 | 16 / 21 | |
| 3.6.11 | 15 / 21 | |
| 3.6.10 | 15 / 21 | |
| 3.6.9 | 15 / 21 | |
| 3.6.8 | 15 / 21 | |
| 3.6.7 | 15 / 21 | |
| 3.6.6 | 15 / 21 | |
| 3.6.5 | 15 / 21 | |
| 3.6.4 | 15 / 21 | |
| 3.6.3 | 15 / 21 | |
| 3.6.2 | 15 / 21 | |
| 3.6.1 | 15 / 21 | |
| 3.6.0 | 15 / 21 | |
| 3.5.13 | 15 / 21 | |
| 3.5.12 | 15 / 21 | |
| 3.5.11 | 15 / 21 | |
| 3.5.10 | 15 / 21 | |
| 3.5.9 | 15 / 21 | |
| 3.5.8 | 15 / 21 | |
| 3.5.7 | 15 / 21 | |
| 3.5.6 | 15 / 21 | |
| 3.5.5 | 15 / 21 | |
| 3.5.4 | 15 / 21 | |
| 3.5.3 | 15 / 21 | |
| 3.5.2 | 15 / 21 | |
| 3.5.1 | 15 / 21 | |
| 3.5.0 | 15 / 21 | |
| 3.4.8 | 15 / 21 | |
| 3.4.7 | 15 / 21 | |
| 3.4.6 | 15 / 21 | |
| 3.4.5 | 15 / 21 | |
| 3.4.4 | 15 / 21 | |
| 3.4.3 | 15 / 21 | |
| 3.4.2 | 15 / 21 | |
| 3.4.1 | 15 / 21 | |
| 3.3.6 | 15 / 21 | |
| 3.3.5 | 15 / 21 |
v3.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.