@avalabs/fusion-sdk
<p align="center"> <a href="https://subnets.avax.network/"> <picture> <img alt="Avalanche Logo" src="https://images.ctfassets.net/gcj8jwzm6086/Gse8dqDEnJtT87RsbbEf4/1609daeb09e9db4a6617d44623028356/Avalanche_Horizontal_White.svg" width="auto" heig
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/transfer-service/avalanche-cct/_handlers/transfer-asset.js | AI (source-diff): Standard tsdown ESM bundle output; code is readable and contains no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/transfer-service/avalanche-cct/_handlers/transfer-asset.cjs | AI (source-diff): Standard tsdown minified bundle output; code is readable and contains no malicious patterns. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from individual publisher to GitHub Actions CI/CD is expected for @avalabs org packages. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions CI; provenance attestation absence is common and not a risk signal for this org. | ai | |
| phantom-deps | phantom-dep:@scure/base | AI (phantom-deps): Declared dependency; bundled output pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:bignumber.js | AI (phantom-deps): Declared dependency; bundled output pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:bitcoinjs-lib | AI (phantom-deps): Declared dependency; bundled output pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:@lombard.finance/sdk | AI (phantom-deps): Declared dependency; bundled output pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:@bitcoinerlab/secp256k1 | AI (phantom-deps): Declared dependency; bundled output pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:@layerzerolabs/lz-v2-utilities | AI (phantom-deps): Declared dependency; bundled output pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:es-toolkit | AI (phantom-deps): Declared dependency; bundled output pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:coinselect | AI (phantom-deps): Declared dependency; phantom-dep heuristic fires on bundled output, not a real phantom. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Bundled SDK; deps declared in package.json and used transitively or re-exported, not a phantom risk. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.17.0 | 9 / 10 | |
| 0.16.0 | 9 / 9 | |
| 0.15.1 | 9 / 9 | |
| 0.15.0 | 9 / 9 | |
| 0.14.4 | 9 / 9 | |
| 0.14.3 | 9 / 9 | |
| 0.14.2 | 9 / 9 | |
| 0.14.1 | 9 / 9 | |
| 0.14.0 | 9 / 9 | |
| 0.13.0 | 9 / 9 | |
| 0.12.0 | 9 / 9 | |
| 0.11.1 | 9 / 9 | |
| 0.11.0 | 9 / 9 | |
| 0.10.0 | 9 / 9 | |
| 0.9.0 | 9 / 9 | |
| 0.8.0 | 9 / 9 | |
| 0.7.0 | 9 / 9 | |
| 0.6.0 | 9 / 9 | |
| 0.5.0 | 9 / 9 | |
| 0.4.0 | 9 / 9 | |
| 0.3.0 | 9 / 9 | |
| 0.2.0 | 9 / 9 | |
| 0.1.0 | 9 / 9 |
v0.17.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.4
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-24. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-24. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-06. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.