@concordium/common-sdk
This package is the shared library for the NodeJS and Web SDK's.
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:grpc/v2/concordium/types.js | AI (source-diff): File is auto-generated by protobuf-ts 2.8.1 from .proto files (header comment confirms this). Long lines are a known artifact of protobuf code generation, not malicious obfuscation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 42 new files are generated protobuf/gRPC artifacts, consistent with the generate-ts-v2 script and @protobuf-ts/plugin devDependency. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is due to generated gRPC v2 protobuf type definitions, a legitimate and expected addition for a blockchain SDK adding gRPC v2 support. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is a fundamental operation in this blockchain SDK, used for credential ID processing and address derivation. Not a malicious payload indicator for this package. | ai | |
| provenance | missing-githead | AI (provenance): Package has a long history with a trusted publisher; missing gitHead appears to reflect a CI/publish environment change, not a malicious publish. No material code changes in this version. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from concordium-shj to soerenbz occurred in Oct 2023 and is a legitimate org-internal maintainer transition; soerenbz has 3 approved packages and 969 days of history. | ai | |
| phantom-deps | phantom-dep:@grpc/grpc-js | AI (phantom-deps): Transitive gRPC dependency referenced in config; standard pattern for gRPC packages; already marked accepted risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Metadata signals (short README, no keywords, inflated semver) are benign for a monorepo SDK package; already marked accepted risk. | ai | |
| dependencies | unvetted-dep:@concordium/rust-bindings | AI (dependencies): Internal Concordium dependency; appropriate for official SDK; already marked accepted risk. | ai | |
| dependencies | unvetted-dep:@protobuf-ts/runtime-rpc | AI (dependencies): Standard protobuf runtime; necessary for gRPC SDK; already marked accepted risk. | ai | |
| dependencies | unvetted-dep:@noble/ed25519 | AI (dependencies): Well-known cryptographic library; appropriate for blockchain SDK; already marked accepted risk. | ai | |
| dependencies | unvetted-dep:iso-3166-1 | AI (dependencies): Standard ISO country code library; appropriate for SDK use; already marked accepted risk. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 9.5.3 | 13 / 20 | |
| 9.5.2 | 13 / 20 | |
| 9.5.1 | 13 / 20 | |
| 9.5.0 | 13 / 20 | |
| 9.4.0 | 13 / 20 | |
| 9.3.0 | 13 / 20 | |
| 9.2.1 | 13 / 20 | |
| 9.2.0 | 13 / 20 | |
| 9.1.1 | 13 / 20 | |
| 9.1.0 | 13 / 20 | |
| 9.0.0 | 12 / 19 | |
| 8.0.0 | 12 / 19 | |
| 7.0.1 | 12 / 19 | |
| 7.0.0 | 12 / 19 | |
| 6.5.0 | 12 / 19 | |
| 6.4.2 | 12 / 19 | |
| 6.4.1 | 12 / 19 | |
| 6.4.0 | 12 / 19 | |
| 6.3.0 | 12 / 19 | |
| 6.2.0 | 10 / 16 | |
| 6.1.0 | 10 / 16 | |
| 6.0.0 | 9 / 16 | |
| 5.2.0 | 9 / 16 | |
| 5.1.0 | 9 / 16 | |
| 5.0.0 | 9 / 16 | |
| 4.0.0 | 9 / 16 | |
| 3.0.0 | 9 / 16 | |
| 2.4.0 | 9 / 16 | |
| 2.3.2 | 8 / 16 | |
| 2.3.1 | 8 / 16 | |
| 2.3.0 | 8 / 16 | |
| 2.2.0 | 8 / 16 | |
| 2.1.1 | 8 / 16 | |
| 2.1.0 | 8 / 16 | |
| 2.0.1 | 8 / 16 | |
| 2.0.0 | 6 / 18 | |
| 1.0.1 | 6 / 18 | |
| 1.0.0 | 5 / 17 |
v9.5.3
2 findingsThis version was published by a different npm account than previous versions on 2023-10-20. 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.
v9.5.2
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-10-20. This could indicate a legitimate maintainer transition or an account compromise.
v9.5.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-19. This could indicate a legitimate maintainer transition or an account compromise.
v9.5.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.
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-19. This could indicate a legitimate maintainer transition or an account compromise.
v9.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.