@xyo-network/sdk-protocol-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/neutral/worker/wasmHash-bundle.mjs | AI (source-diff): Same bundled WASM blob, neutral target build. | ai | |
| source-diff | encoded-string-file:dist/browser/worker/wasmHash-bundle.mjs | AI (source-diff): WASM binary blobs from bundled hash-wasm dep, not obfuscated payload. | ai | |
| source-diff | encoded-string-file:dist/node/worker/wasmHash-bundle.mjs | AI (source-diff): Same bundled hash-wasm WASM data, esbuild output. | ai | |
| phantom-deps | phantom-dep:observable-fns | AI (phantom-deps): Used indirectly via config/threads tooling; not suspicious. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 7.2.2 | 11 / 18 | |
| 7.2.1 | 11 / 18 | |
| 7.2.0 | 10 / 18 | |
| 7.1.0 | 10 / 18 | |
| 7.0.16 | 9 / 21 |
v7.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 22 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.
v7.2.0
4 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 22 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.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.