@polkadot-api/sdk-ink
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/esm/.papi/descriptors/dist/metadataTypes-PFA3TI6G.mjs | AI (source-diff): SCALE-encoded chain metadata as base64 string — standard papi codegen output. | ai | |
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Same SCALE/base64 metadata blobs bundled into dist/index.js — expected papi build artifact. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by bundled chain metadata descriptors (741KB .mjs files) added in this version. | ai | |
| source-diff | obfuscated-file:dist/esm/.papi/descriptors/dist/descriptors-GFVXYJWQ.mjs | AI (source-diff): Polkadot chain descriptor JSON blob — standard papi codegen output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/.papi/descriptors/dist/wndAh_metadata-ZNXXSRSB.mjs | AI (source-diff): SCALE-encoded Westend Asset Hub metadata — standard papi codegen output. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata is typical for polkadot-api ecosystem scoped packages; not indicative of malice. | ai | |
| phantom-deps | phantom-dep:abitype | AI (phantom-deps): abitype is a declared runtime dep used for type-level utilities; phantom-dep false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 6 / 3 | |
| 0.6.0 | 5 / 3 | |
| 0.5.1 | 5 / 3 | |
| 0.5.0 | 5 / 3 | |
| 0.4.4 | 3 / 3 | |
| 0.4.3 | 3 / 3 | |
| 0.4.2 | 4 / 3 | |
| 0.4.1 | 4 / 3 | |
| 0.4.0 | 4 / 3 | |
| 0.3.2 | 3 / 3 | |
| 0.3.1 | 3 / 3 | |
| 0.3.0 | 3 / 3 | |
| 0.2.0 | 3 / 3 | |
| 0.1.0 | 1 / 3 |
v0.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.