@debridge-finance/intents-client
SDK for working with the intents program in Solana. Allows creating, managing, and executing intents for cross-chain operations.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@debridge-finance/solana-tx-sender | AI (dependencies): Same-org dependency from a publisher with a clean track record; stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established debridge-finance package; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:tweetnacl | AI (phantom-deps): tweetnacl is a declared dep used transitively by Solana libs; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@debridge-finance/solana-tx-sender | AI (phantom-deps): Same-org scope; phantom-dep heuristic fires on intra-org deps that may be re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:bs58 | AI (phantom-deps): Likely used transitively or in type declarations; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:bn.js | AI (phantom-deps): Likely used transitively or in type declarations; stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.7.0 | 10 / 10 | |
| 1.4.0 | 10 / 10 | |
| 1.3.1 | 10 / 10 | |
| 1.3.0 | 10 / 10 | |
| 1.2.6 | 10 / 10 | |
| 1.2.1 | 10 / 10 | |
| 1.1.0 | 10 / 10 |
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (scrobot.debridge) than the most recent previously approved version (de_totoro) on 2025-12-25, but scrobot.debridge is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.