@concordium/rust-bindings
[](https://github.com/Concordium/.github/blob/main/.github/CODE_OF_CONDUCT.md)
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 | source-size-tripled | AI (source-diff): Size increase is due to shipping pre-compiled WASM binaries and their JS wrappers for multiple targets (web/node/bundler/react-native). Expected for a major version of a Rust/WASM package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New files are wasm-pack generated WASM glue code for wallet build target. Expected for a Rust WASM bindings package expanding its build targets. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to concordium-npm-ci, an established CI account (11 approved packages, 708 days old) within the Concordium org. This is a legitimate org-level CI publishing consolidation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers concordium-npm-ci and opsnpm are Concordium org CI accounts. Legitimate organizational publishing consolidation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Previous individual maintainers removed as part of Concordium org transition to CI-based publishing. Consistent with organizational practice. | ai | |
| source-diff | net-exec-file:lib/wallet/node/umd/index.min.js | AI (source-diff): Minified wasm-bindgen/webpack bundle for Node.js UMD target. Content is base64/buffer utilities and WASM glue — standard for this Rust bindings package. | ai | |
| source-diff | net-exec-file:lib/wallet/web/umd/index.min.js | AI (source-diff): Minified wasm-bindgen/webpack bundle for web UMD target. Same pattern as node UMD — standard output for this Rust bindings package. | ai | |
| source-diff | net-exec-file:lib/wallet/web/esm/index.min.js | AI (source-diff): Minified webpack bundle of wasm-bindgen output; expected distribution artifact for this WASM binding package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): wasm-bindgen generates __wbg_newnoargs_* exports using new Function() to expose JS constructors to WASM. This is a known, benign wasm-bindgen pattern. | ai | |
| source-diff | obfuscated-file:lib/dapp/react-native/index_bg.wasm.js | AI (source-diff): This is wasm-bindgen generated code embedding WASM binary as base64. Long lines are inherent to this output format, not obfuscation. Stable pattern for this package. | ai | |
| source-diff | net-exec-file:lib/wallet/web/esm/index.js | AI (source-diff): Standard wasm-bindgen JS glue code for WASM memory/heap management. Not a dropper; this is the canonical output of wasm-pack for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Concordium SDK package with 38 versions and 1429 days of history. Low README quality is not a risk signal for this type of library. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() in wasm-bindgen output is standard JS interop for WASM host bindings. Not evasion; this is expected in all wasm-bindgen generated glue code. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 4.0.1 | 0 / 13 | |
| 4.0.0 | 0 / 13 | |
| 3.3.0 | 0 / 14 | |
| 3.2.1 | 0 / 14 | |
| 3.2.0 | 0 / 14 | |
| 3.1.0 | 0 / 12 | |
| 3.0.0 | 0 / 12 | |
| 2.0.1 | 0 / 12 | |
| 1.2.0 | 0 / 0 | |
| 1.1.0 | 0 / 0 | |
| 1.0.0 | 0 / 0 | |
| 0.12.0 | 0 / 0 | |
| 0.11.1 | 0 / 0 | |
| 0.11.0 | 0 / 0 | |
| 0.10.0 | 0 / 0 | |
| 0.9.0 | 0 / 0 | |
| 0.8.0 | 0 / 0 | |
| 0.7.0 | 0 / 0 | |
| 0.6.0 | 0 / 0 | |
| 0.5.0 | 0 / 0 | |
| 0.4.0 | 0 / 0 | |
| 0.3.0 | 0 / 0 | |
| 0.2.0 | 0 / 0 | |
| 0.1.1 | 0 / 0 | |
| 0.1.0 | 0 / 0 |
v4.0.1
7 findingsThis version was published by a different npm account than previous versions on 2026-01-14. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-07. 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.
v3.3.0
2 findingsThis version was published by a different npm account than previous versions on 2025-04-09. 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.
v3.2.1
2 findingsThis version was published by a different npm account than previous versions on 2024-08-07. 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.
v3.2.0
2 findingsThis version was published by a different npm account than previous versions on 2024-07-05. 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.
v3.1.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: soerenbz.
This version was published by a different npm account than previous versions on 2024-05-15. 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.
v3.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: concordium-joe.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-01-11. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: soerenbz.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-10-31. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-06-27. This could indicate a legitimate maintainer transition or an account compromise.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.