clarinet — Greenflagged

SAX based evented streaming JSON parser in JavaScript (browser and node)

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

thejhdscapeevan-king

Keywords

saxjsonparserstreamstreamingeventeventsemitterasyncstreamerbrowser

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
install-scripts	install-script:postinstall	AI (install-scripts): Postinstall runs 'cd benchmark && npm i' — installs local benchmark dependencies only. No remote code execution or arbitrary downloads. Stable benign pattern for this package.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require in benchmark/index.js loads JSON sample files by name from a local directory — not arbitrary user input. Benign pattern for this package.	ai	2026/04/24
source-diff	net-exec-file:benchmark/node_modules/benchmark/benchmark.js	AI (source-diff): This is the canonical benchmark.js library (MIT, Mathias Bynens/JDD) vendored in the benchmark sub-package. Not malware; stable false positive for this package.	ai	2026/04/24
source-diff	net-exec-file:benchmark/node_modules/jade/jade.js	AI (source-diff): This is the canonical jade template engine vendored in the benchmark sub-package. Not malware; stable false positive for this package.	ai	2026/04/24
source-diff	net-exec-file:benchmark/node_modules/jade/jade.min.js	AI (source-diff): Minified jade template engine vendored in benchmark sub-package. Not malware; stable false positive for this package.	ai	2026/04/24
source-diff	net-exec-file:test/lib/jquery.js	AI (source-diff): jQuery v1.7.1 test fixture. Network calls and dynamic code execution are intrinsic to jQuery's AJAX and DOM features, not malicious behavior.	ai	2026/04/24
source-diff	obfuscated-file:test/lib/jquery.js	AI (source-diff): This is jQuery v1.7.1 minified, bundled as a test fixture. The file header confirms its identity. Minification naturally produces long lines; not obfuscation or malware.	ai	2026/04/24
source-diff	net-exec-file:test/lib/underscore.js	AI (source-diff): Underscore.js 1.2.3 test fixture. Dynamic code execution (template engine) and AMD/CommonJS module detection are standard Underscore features, not malicious.	ai	2026/04/24
source-diff	source-size-tripled	AI (source-diff): Size increase is due to large test fixtures (13.7MB Twitter JSON sample, minified jQuery/Underscore/Mocha). No runtime payload added.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change (dscape → thejh) occurred in January 2012, over 13 years ago. thejh has a clean track record and this is a well-established package. Not a current risk.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance by many years; absence of attestation is expected and not a risk signal for this era of package.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): Maintainer addition is from 2012 and reflects a historical, legitimate transition. No ongoing risk for this long-established package.	ai	2026/04/24

Versions (showing 30 of 30)

Version	Deps	Published
0.12.6	0 / 3	2023-08-24
0.12.5	0 / 3	2022-01-07
0.12.4	0 / 3	2019-10-18
0.12.3	0 / 3	2019-01-05
0.12.2	0 / 3	2019-01-04
0.12.1	0 / 3	2018-07-19
0.12.0	0 / 3	2018-01-03
0.11.0	0 / 3	2015-05-11
0.10.0	0 / 3	2015-01-09
0.9.1	0 / 3	2015-01-02
0.9.0	0 / 3	2014-07-02
0.8.1	0 / 3	2014-02-17
0.8.0	0 / 3	2014-01-16
0.7.3	0 / 3	2013-12-15
0.7.2	0 / 3	2013-06-18
0.7.1	0 / 3	2012-12-03
0.7.0	0 / 3	2012-10-30
0.6.0	0 / 3	2012-06-08
0.5.8	0 / 3	2012-03-26
0.5.7	0 / 3	2012-01-17
0.5.6	0 / 3	2012-01-16
0.5.5	0 / 3	2011-12-23
0.5.4	0 / 3	2011-12-22
0.5.3	0 / 3	2011-12-22
0.5.2	0 / 3	2011-12-22
0.5.1	0 / 3	2011-12-21
0.5.0	0 / 3	2011-12-20
0.4.1	0 / 3	2011-12-19
0.4.0	0 / 3	2011-12-19
0.3.5	0 / 0	2011-12-16

v0.12.6

1 finding

LOW No provenance attestation provenance

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

v0.12.5

1 finding

INFO No provenance attestation provenance

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

v0.12.4

1 finding

LOW No provenance attestation provenance

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

v0.12.3

4 findings

HIGH New file with network + code execution: benchmark/node_modules/benchmark/benchmark.js source-diff

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

HIGH New file with network + code execution: benchmark/node_modules/jade/jade.js source-diff

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

HIGH New file with network + code execution: benchmark/node_modules/jade/jade.min.js source-diff

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

INFO No provenance attestation provenance

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

v0.12.2

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: cd benchmark && npm i

INFO No provenance attestation provenance

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

v0.12.1

1 finding

INFO No provenance attestation provenance

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

v0.12.0

2 findings

HIGH Publisher changed: dscape → evan-king (on 2018-01-03) provenance

This version was published by a different npm account than previous versions on 2018-01-03. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.11.0

1 finding

INFO No provenance attestation provenance

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

v0.10.0

1 finding

INFO No provenance attestation provenance

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

v0.9.1

1 finding

INFO No provenance attestation provenance

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

v0.9.0

1 finding

INFO No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

INFO No provenance attestation provenance

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

v0.7.3

1 finding

INFO No provenance attestation provenance

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

v0.7.2

1 finding

INFO No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

INFO No provenance attestation provenance

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

v0.6.0

1 finding

INFO No provenance attestation provenance

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

v0.5.8

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: thejh → dscape (on 2012-03-26) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2012-03-26. This could indicate a legitimate maintainer transition or an account compromise.

v0.5.7

1 finding

INFO No provenance attestation provenance

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

v0.5.6

2 findings

HIGH Publisher changed: dscape → thejh (on 2012-01-16) provenance

This version was published by a different npm account than previous versions on 2012-01-16. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.5.5

1 finding

INFO No provenance attestation provenance

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

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

4 findings

HIGH New obfuscated file: test/lib/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: test/lib/jquery.js source-diff

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

HIGH New file with network + code execution: test/lib/underscore.js source-diff

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

INFO No provenance attestation provenance

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

v0.5.0

4 findings

HIGH New obfuscated file: test/lib/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: test/lib/jquery.js source-diff

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

HIGH New file with network + code execution: test/lib/underscore.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.4.1

4 findings

HIGH New obfuscated file: test/lib/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: test/lib/jquery.js source-diff

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

HIGH New file with network + code execution: test/lib/underscore.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.4.0

4 findings

HIGH New obfuscated file: test/lib/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: test/lib/jquery.js source-diff

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

HIGH New file with network + code execution: test/lib/underscore.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.3.5

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.