@jitl/quickjs-singlefile-mjs-release-sync No license 2 versions

@jitl/quickjs-singlefile-mjs-release-sync

npm Repository

Versions

—

License

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

jitl

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/emscripten-module-Q67P5WYC.mjs	AI (source-diff): Emscripten-compiled WASM bundle; minified output is expected and stable for this package.	ai	2026/05/18

Versions (showing 2 of 2)

Version	Deps	Published
0.32.0	1 / 0	2026-02-16
0.31.0	1 / 0	2024-09-07

v0.32.0

2 findings

HIGH New obfuscated file: dist/emscripten-module-Q67P5WYC.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.31.0

1 finding

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.