@defuse-protocol/intents-sdk
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:omni-bridge-sdk | AI (phantom-deps): omni-bridge-sdk is a declared dependency used via config/re-export pattern; stable false positive for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are established ecosystem packages (solana/web3.js, valibot, etc.) consistent with multi-chain SDK expansion. | ai | |
| source-diff | large-new-source-files | AI (source-diff): SDK bundles chain-specific deps (Solana, NEAR) into dist/node_modules; large file counts are expected for this package. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size growth driven by bundled @solana/web3.js and related libs; consistent with expanding multi-chain SDK scope. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 108 versions; provenance not historically used, low risk. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of human maintainer consistent with migration to automated CI/CD publishing via GitHub Actions. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation is a legitimate and more secure publishing pattern for this org. | ai | |
| phantom-deps | phantom-dep:@near-js/keystores | AI (phantom-deps): NEAR SDK deps referenced in config/type files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@near-js/accounts | AI (phantom-deps): NEAR SDK deps referenced in config/type files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@near-js/client | AI (phantom-deps): NEAR SDK deps referenced in config/type files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lifeomic/attempt | AI (phantom-deps): @lifeomic/attempt is a declared runtime dep; phantom-dep heuristic fires incorrectly for bundled SDK packages. | ai |
Versions (showing 77 of 77)
| Version | Deps | Published |
|---|---|---|
| 0.67.1 | 16 / 2 | |
| 0.67.0 | 16 / 2 | |
| 0.66.1 | 16 / 2 | |
| 0.66.0 | 16 / 2 | |
| 0.65.0 | 16 / 2 | |
| 0.64.1 | 16 / 2 | |
| 0.64.0 | 16 / 1 | |
| 0.63.2 | 16 / 1 | |
| 0.63.1 | 16 / 1 | |
| 0.63.0 | 16 / 1 | |
| 0.62.2 | 16 / 1 | |
| 0.62.1 | 16 / 1 | |
| 0.62.0 | 16 / 1 | |
| 0.61.0 | 16 / 1 | |
| 0.60.0 | 16 / 1 | |
| 0.59.1 | 16 / 1 | |
| 0.59.0 | 16 / 1 | |
| 0.58.2 | 16 / 1 | |
| 0.58.1 | 16 / 1 | |
| 0.58.0 | 16 / 1 | |
| 0.57.0 | 16 / 1 | |
| 0.56.1 | 16 / 1 | |
| 0.56.0 | 16 / 1 | |
| 0.55.1 | 16 / 1 | |
| 0.55.0 | 16 / 1 | |
| 0.54.0 | 16 / 1 | |
| 0.53.3 | 16 / 1 | |
| 0.53.2 | 16 / 1 | |
| 0.53.1 | 16 / 1 | |
| 0.53.0 | 16 / 1 | |
| 0.52.0 | 16 / 1 | |
| 0.51.0 | 16 / 1 | |
| 0.50.0 | 16 / 1 | |
| 0.49.0 | 18 / 1 | |
| 0.48.0 | 18 / 1 | |
| 0.47.0 | 18 / 1 | |
| 0.46.0 | 18 / 1 | |
| 0.45.0 | 18 / 1 | |
| 0.44.0 | 18 / 1 | |
| 0.43.3 | 18 / 2 | |
| 0.43.1 | 18 / 2 | |
| 0.43.0 | 18 / 2 | |
| 0.39.1 | 18 / 2 | |
| 0.39.0 | 18 / 2 | |
| 0.38.1 | 18 / 2 | |
| 0.37.0 | 18 / 2 | |
| 0.36.1 | 18 / 2 | |
| 0.34.0 | 18 / 2 | |
| 0.33.2 | 18 / 2 | |
| 0.33.0 | 18 / 2 | |
| 0.31.0 | 18 / 2 | |
| 0.30.1 | 18 / 2 | |
| 0.30.0 | 18 / 2 | |
| 0.29.1 | 18 / 2 | |
| 0.29.0 | 18 / 2 | |
| 0.27.0 | 18 / 2 | |
| 0.26.4 | 18 / 2 | |
| 0.26.3 | 18 / 2 | |
| 0.26.0 | 16 / 2 | |
| 0.25.0 | 16 / 2 | |
| 0.24.0 | 16 / 2 | |
| 0.23.1 | 15 / 2 | |
| 0.23.0 | 15 / 2 | |
| 0.22.1 | 13 / 2 | |
| 0.20.1 | 13 / 2 | |
| 0.20.0 | 13 / 2 | |
| 0.19.3 | 13 / 2 | |
| 0.19.2 | 13 / 2 | |
| 0.19.1 | 13 / 2 | |
| 0.19.0 | 13 / 2 | |
| 0.18.0 | 13 / 2 | |
| 0.17.0 | 13 / 2 | |
| 0.16.2 | 13 / 3 | |
| 0.16.1 | 13 / 3 | |
| 0.16.0 | 13 / 3 | |
| 0.15.0 | 13 / 3 | |
| 0.14.0 | 9 / 3 |
v0.67.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.67.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.66.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.66.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.64.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.62.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.62.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.