@axelar-network/axelarjs-sdk
The JavaScript SDK for Axelar Network
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Long-established Axelar SDK; absence of provenance is common and not a risk signal here. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Long-standing postinstall in this SDK; runs a local JS script, not a remote fetch. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a declared runtime dep used transitively via socket.io-client; phantom detection is a false positive here. | ai | |
| phantom-deps | phantom-dep:@types/uuid | AI (phantom-deps): Type-only package; not directly imported at runtime by design. | ai | |
| phantom-deps | phantom-dep:@axelar-network/axelar-cgp-solidity | AI (phantom-deps): Same-org package used in compile script; phantom detection is a false positive for this build-time usage. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.21.0 | 22 / 32 | |
| 0.20.0 | 22 / 32 | |
| 0.19.1 | 22 / 32 | |
| 0.19.0 | 22 / 32 | |
| 0.18.0 | 22 / 32 | |
| 0.17.4 | 20 / 31 |
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
2 findingsScript: node scripts/postinstall.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.