@multiversx/sdk-core
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 |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is fundamental to blockchain SDK operations (address encoding, ABI serialization, transaction data). All instances are legitimate data handling, not obfuscated payloads. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is used for smart contract query response data — standard blockchain SDK usage, not malicious payload hiding. | ai | |
| phantom-deps | phantom-dep:@multiversx/sdk-transaction-decoder | AI (phantom-deps): Same org-scope dependency; likely used indirectly or via type imports in the compiled TypeScript output. Stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 15.4.1 | 16 / 19 | |
| 15.4.0 | 16 / 19 | |
| 15.3.2 | 16 / 19 | |
| 15.3.1 | 16 / 19 | |
| 15.3.0 | 16 / 19 | |
| 15.2.0 | 16 / 19 | |
| 15.1.1 | 16 / 19 | |
| 15.1.0 | 16 / 19 | |
| 15.0.1 | 16 / 19 | |
| 15.0.0 | 16 / 19 |
v15.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.