lexical-scope — Greenflagged

detect global and local lexical identifiers from javascript source code

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

substackzertosh

Keywords

astvariablenamelexicallocalglobalimplicitexported

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:bench/jquery.js	AI (source-diff): bench/jquery.js is the canonical minified jQuery v1.7.1 included as a benchmark fixture for AST parsing. Not malicious; stable false positive for this package.	ai	2026/04/24
source-diff	net-exec-file:bench/jquery.js	AI (source-diff): Network and dynamic execution patterns in bench/jquery.js are jQuery's own AJAX and Function constructor internals, not dropper/loader malware. Stable false positive for this package.	ai	2026/04/24
semgrep	semgrep:new-function-constructor	AI (semgrep): new Function() usage is in the bundled jQuery v1.7.1 benchmark fixture, not in the package's runtime code. Stable false positive for this package.	ai	2026/04/24
npm-metadata	suspicious-initial-version	AI (npm-metadata): Package is 13+ years old by trusted publisher substack; 0.0.0 is a legitimate versioning choice, not an indicator of malicious intent for this well-established package.	ai	2026/04/24

Versions (showing 19 of 19)

Version	Deps	Published
1.2.0	1 / 2	2015-09-18
1.1.1	1 / 2	2015-04-25
1.1.0	1 / 2	2014-03-18
1.0.0	1 / 2	2014-03-05
0.1.0	1 / 2	2014-02-01
0.0.15	1 / 3	2013-12-20
0.0.14	1 / 3	2013-06-23
0.0.13	1 / 4	2013-06-05
0.0.12	1 / 4	2013-05-31
0.0.11	1 / 4	2013-05-21
0.0.10	1 / 4	2013-03-31
0.0.9	1 / 4	2013-03-30
0.0.8	1 / 4	2013-03-30
0.0.7	1 / 3	2013-03-30
0.0.6	1 / 2	2013-03-02
0.0.5	1 / 2	2013-03-02
0.0.3	1 / 2	2013-02-20
0.0.1	1 / 2	2013-02-18
0.0.0	1 / 2	2013-02-17

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.0

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.15

1 finding

LOW No provenance attestation provenance

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

v0.0.14

1 finding

LOW No provenance attestation provenance

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

v0.0.13

1 finding

LOW No provenance attestation provenance

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

v0.0.12

1 finding

LOW No provenance attestation provenance

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

v0.0.11

1 finding

LOW No provenance attestation provenance

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

v0.0.10

1 finding

LOW No provenance attestation provenance

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

v0.0.9

1 finding

LOW No provenance attestation provenance

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

v0.0.8

1 finding

LOW No provenance attestation provenance

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

v0.0.7

1 finding

LOW No provenance attestation provenance

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

v0.0.6

1 finding

LOW No provenance attestation provenance

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

v0.0.5

3 findings

HIGH New obfuscated file: bench/jquery.js source-diff

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

HIGH New file with network + code execution: bench/jquery.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.0.3

1 finding

LOW No provenance attestation provenance

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

v0.0.1

1 finding

LOW No provenance attestation provenance

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

v0.0.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.