← Home

@chainsafe/as-sha256

npm Repository Homepage
6
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

wemeetagainmatthewkeil

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): Compiled AssemblyScript wasm build output from documented asbuild scripts; stable for this package. ai

Versions (showing 6 of 6)

Version Deps Published
1.2.4 0 / 2
1.2.3 0 / 2
1.2.0 0 / 2
1.1.0 0 / 2
1.0.1 0 / 2
1.0.0 0 / 2

v1.1.0

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • build/optimized.simd.wasm • build/optimized.wasm • build/untouched.simd.wasm • build/untouched.wasm

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.1

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • build/optimized.simd.wasm • build/optimized.wasm • build/untouched.simd.wasm • build/untouched.wasm

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • build/optimized.simd.wasm • build/optimized.wasm • build/untouched.simd.wasm • build/untouched.wasm

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.