jshint — Greenflagged

Static analysis tool for JavaScript

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

jugglinmikeantonkovalyovrwaldron

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	url-dep:esprima	AI (npm-metadata): Historical artifact of early JSHint versions when esprima wasn't on npm; not a malicious signal for this well-established package.	ai	2026/04/24
source-diff	net-exec-file:dist/jshint.js	AI (source-diff): dist/jshint.js is JSHint's standard browserify build artifact. The 'network+exec' pattern is the browserify module loader, not malware. Stable false positive for this package.	ai	2026/04/24
source-diff	net-exec-file:dist/jshint-rhino.js	AI (source-diff): dist/jshint-rhino.js is JSHint's standard browserify build artifact for Rhino environments. The 'network+exec' pattern is the browserify module loader, not malware. Stable false positive for this package.	ai	2026/04/24
source-diff	source-size-tripled	AI (source-diff): Size increase is explained by addition of two large dist/ build artifacts (~741KB + ~738KB), which are expected compiled outputs for a linter shipping browser/Rhino builds.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): The antonkovalyov → rwaldron transition in 2014 is a well-documented legitimate maintainer handoff for the JSHint project; stable historical fact for this package.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): rwaldron is a known JS community contributor; this maintainer addition in 2014 is a legitimate historical transition, not a compromise.	ai	2026/04/24
source-diff	obfuscated-file:data/es5-identifier-names.js	AI (source-diff): This file is a generated regex of Unicode character ranges for ES5 identifier validation — long lines are inherent to the data format, not obfuscation. Stable false positive for jshint.	ai	2026/04/24
typosquat	typosquat.levenshtein:eslint	AI (typosquat): JSHint is a well-known, long-established JS linting tool that predates ESLint. The name similarity is coincidental; this is not a typosquat.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): htmlparser2 is a well-established HTML parser added for inline HTML linting support. No malicious history; legitimate feature addition.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require in JSHint's CLI is used to load user config files (jshintConfig). This is the documented config-loading mechanism, not arbitrary code execution.	ai	2026/04/24

Versions (showing 95 of 95)

Version	Deps	Published
2.13.6	7 / 16	2022-11-11
2.13.5	7 / 16	2022-07-08
2.13.4	7 / 16	2022-01-24
2.13.3	8 / 16	2022-01-05
2.13.2	8 / 16	2021-12-27
2.13.1	8 / 16	2021-08-10
2.13.0	8 / 16	2021-05-30
2.12.0	8 / 16	2020-08-03
2.11.2	8 / 16	2020-07-30
2.11.1	8 / 16	2020-05-14
2.11.0	8 / 17	2020-01-13
2.10.3	8 / 17	2019-11-05
2.10.2	8 / 17	2019-03-13
2.10.1	8 / 17	2019-02-05
2.10.0	8 / 17	2019-02-05
2.9.7	8 / 17	2018-12-07
2.9.6	11 / 14	2018-07-30
2.9.5	8 / 14	2017-06-22
2.9.4	8 / 13	2016-10-20
2.9.3	8 / 14	2016-08-18
2.9.2	8 / 14	2016-04-19
2.9.1	8 / 14	2016-01-14
2.8.0	8 / 10	2015-05-31
2.7.0	8 / 10	2015-04-11
2.6.3	8 / 10	2015-02-28
2.6.2	8 / 10	2015-02-28
2.6.1	8 / 10	2015-02-27
2.6.0	8 / 10	2015-01-21
2.5.11	8 / 9	2014-12-18
2.5.10	8 / 8	2014-11-06
2.5.9	8 / 8	2014-11-06
2.5.8	8 / 8	2014-10-29
2.5.7	8 / 8	2014-10-28
2.5.6	8 / 7	2014-09-21
2.5.5	8 / 7	2014-08-24
2.5.4	8 / 7	2014-08-18
2.5.3	8 / 7	2014-08-08
2.5.2	8 / 7	2014-07-05
2.5.1	8 / 7	2014-05-16
2.5.0	8 / 8	2014-04-02
2.4.4	7 / 8	2014-02-21
2.4.3	6 / 8	2014-01-26
2.4.2	6 / 8	2014-01-21
2.4.1	6 / 8	2014-01-03
2.4.0	6 / 8	2013-12-25
2.3.0	5 / 8	2013-10-21
2.2.0	5 / 8	2013-10-18
2.1.11	5 / 6	2013-09-20
2.1.10	5 / 6	2013-08-15
2.1.9	5 / 6	2013-08-02
2.1.8	5 / 6	2013-08-01
2.1.7	5 / 6	2013-07-29
2.1.6	5 / 6	2013-07-29
2.1.5	5 / 6	2013-07-27
2.1.4	5 / 6	2013-06-24
2.1.3	5 / 6	2013-06-03
2.1.2	5 / 6	2013-05-22
2.1.1	5 / 6	2013-05-21
2.1.0	5 / 6	2013-05-21
2.0.1	5 / 6	2013-05-08
2.0.0	4 / 7	2013-05-08
1.1.0	6 / 6	2013-03-06
1.0.0	6 / 6	2013-02-21
0.9.1	2 / 1	2012-09-25
0.9.0	2 / 1	2012-09-03
0.8.2	2 / 1	2012-08-30
0.8.1	2 / 1	2012-08-27
0.8.0	2 / 1	2012-08-20
0.7.3	2 / 1	2012-08-06
0.7.2	2 / 1	2012-07-26
0.7.1	2 / 1	2012-05-17
0.7.0	2 / 1	2012-05-08
0.6.3	2 / 1	2012-05-02
0.6.2	2 / 1	2012-04-30
0.6.1	2 / 1	2012-04-11
0.6.0	2 / 1	2012-04-04
0.5.9	2 / 1	2012-02-28
0.5.8	2 / 1	2012-02-14
0.5.7	2 / 1	2012-01-20
0.5.6	2 / 1	2012-01-10
0.5.5	2 / 1	2011-12-12
0.5.4	2 / 1	2011-12-09
0.5.3	2 / 1	2011-12-06
0.5.2	2 / 1	2011-10-27
0.5.1	2 / 1	2011-10-15
0.5.0	3 / 0	2011-10-13
0.4.0	3 / 0	2011-10-11
0.3.1	2 / 0	2011-09-05
0.3.0	2 / 0	2011-08-20
0.2.3	1 / 0	2011-06-22
0.2.2	1 / 0	2011-05-26
0.2.1	1 / 0	2011-05-06
0.2.0	1 / 0	2011-04-07
0.1.9	1 / 0	2011-03-30
0.1.8	1 / 0	2011-03-27

v2.13.6

1 finding

LOW No provenance attestation provenance

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

v2.13.5

1 finding

LOW No provenance attestation provenance

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

v2.13.4

1 finding

LOW No provenance attestation provenance

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

v2.13.3

1 finding

LOW No provenance attestation provenance

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

v2.13.2

1 finding

LOW No provenance attestation provenance

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

v2.13.1

1 finding

LOW No provenance attestation provenance

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

v2.13.0

1 finding

LOW No provenance attestation provenance

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

v2.12.0

1 finding

LOW No provenance attestation provenance

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

v2.11.2

1 finding

LOW No provenance attestation provenance

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

v2.11.1

1 finding

LOW No provenance attestation provenance

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

v2.11.0

1 finding

LOW No provenance attestation provenance

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

v2.10.3

1 finding

LOW No provenance attestation provenance

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

v2.10.2

1 finding

LOW No provenance attestation provenance

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

v2.10.1

1 finding

LOW No provenance attestation provenance

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

v2.10.0

2 findings

HIGH New obfuscated file: data/es5-identifier-names.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.

LOW No provenance attestation provenance

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

v2.9.7

2 findings

HIGH New obfuscated file: data/es5-identifier-names.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.

LOW No provenance attestation provenance

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

v2.9.6

2 findings

HIGH New obfuscated file: data/es5-identifier-names.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.

LOW No provenance attestation provenance

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

v2.9.5

1 finding

LOW No provenance attestation provenance

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

v2.9.4

1 finding

LOW No provenance attestation provenance

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

v2.9.3

1 finding

LOW No provenance attestation provenance

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

v2.9.2

1 finding

LOW No provenance attestation provenance

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

v2.9.1

2 findings

HIGH Publisher changed: rwaldron → jugglinmike (on 2016-01-14) provenance

This version was published by a different npm account than previous versions on 2016-01-14. 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.

v2.8.0

2 findings

HIGH Publisher changed: rwaldron → jugglinmike (on 2015-05-31) provenance

This version was published by a different npm account than previous versions on 2015-05-31. 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.

v2.7.0

1 finding

LOW No provenance attestation provenance

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

v2.6.3

1 finding

LOW No provenance attestation provenance

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

v2.6.2

1 finding

LOW No provenance attestation provenance

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

v2.6.1

1 finding

LOW No provenance attestation provenance

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

v2.6.0

1 finding

LOW No provenance attestation provenance

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

v2.5.11

1 finding

LOW No provenance attestation provenance

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

v2.5.10

1 finding

LOW No provenance attestation provenance

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

v2.5.9

1 finding

LOW No provenance attestation provenance

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

v2.5.8

1 finding

LOW No provenance attestation provenance

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

v2.5.7

1 finding

LOW No provenance attestation provenance

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

v2.5.6

1 finding

LOW No provenance attestation provenance

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

v2.5.5

1 finding

LOW No provenance attestation provenance

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

v2.5.4

2 findings

HIGH Publisher changed: antonkovalyov → rwaldron (on 2014-08-18) provenance

This version was published by a different npm account than previous versions on 2014-08-18. 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.

v2.5.3

2 findings

HIGH Publisher changed: antonkovalyov → rwaldron (on 2014-08-08) provenance

This version was published by a different npm account than previous versions on 2014-08-08. 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.

v2.5.2

1 finding

LOW No provenance attestation provenance

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

v2.5.1

3 findings

HIGH New file with network + code execution: dist/jshint-rhino.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: dist/jshint.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.

v2.5.0

1 finding

LOW No provenance attestation provenance

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

v2.4.4

1 finding

LOW No provenance attestation provenance

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

v2.4.3

1 finding

LOW No provenance attestation provenance

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

v2.4.2

1 finding

LOW No provenance attestation provenance

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

v2.4.1

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.11

1 finding

LOW No provenance attestation provenance

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

v2.1.10

1 finding

LOW No provenance attestation provenance

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

v2.1.9

1 finding

LOW No provenance attestation provenance

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

v2.1.8

1 finding

LOW No provenance attestation provenance

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

v2.1.7

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.

v2.1.6

1 finding

LOW No provenance attestation provenance

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

v2.1.5

1 finding

LOW No provenance attestation provenance

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

v2.1.4

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.

v2.1.3

1 finding

LOW No provenance attestation provenance

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

v2.1.2

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.

v2.1.1

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.

v2.1.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.

v2.0.1

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.

v2.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.

v1.1.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.

v1.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.