cjs-module-lexer — Greenflagged

Lexes CommonJS modules, returning their named exports metadata

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

guybedfordmhdawson1nodejs-foundation

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	encoded-string-file:dist/lexer.js	AI (source-diff): The long base64 string is the inlined WebAssembly binary (lexer.wasm), a documented and stable build pattern for this package. Not a malicious payload.	ai	2026/04/27
source-diff	encoded-string-file:dist/lexer.mjs	AI (source-diff): Same inlined WASM binary in the ESM build. Stable false positive for this package's build pattern.	ai	2026/04/27
maintainer-change	maintainer-added	AI (maintainer-change): mhdawson1 (Michael Dawson) is a Node.js TSC member; addition is consistent with this package being under the nodejs GitHub org.	ai	2026/04/27

Versions (showing 3 of 3)

Version	Deps	Published
2.2.0	0 / 7	2026-01-02
2.1.1	0 / 7	2025-11-07
1.2.3	0 / 6	2023-06-10

v2.1.1

3 findings

HIGH Long encoded string in modified file: dist/lexer.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: dist/lexer.mjs source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v1.2.3

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.