@axelar-network/axelar-gmp-sdk-solidity
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): eng_axelar is the Axelar org account with 5 approved packages; transition from individual to org account is expected. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires in hardhat.config.js loading chain config JSON by env var — standard dev tooling pattern, not a runtime risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Solidity contract SDK; sparse README and no keywords are normal for this package type. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 6.2.0 | 0 / 17 | |
| 6.1.0 | 0 / 17 | |
| 6.0.6 | 0 / 16 | |
| 5.10.0 | 0 / 14 |
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.