gulp-jshint — Greenflagged

JSHint plugin for gulp

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

contraspalgerfractal

Keywords

gulpplugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from spalger to contra occurred in 2016; contra has a strong track record (226 approved packages). This is a historical legitimate maintainer transition, not a compromise.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require of userOpts.linter is an intentional, documented feature allowing custom linter modules. Not an attack vector for this package.	ai	2026/04/23
publish-pattern	new-deps-added	AI (publish-pattern): plugin-error is the canonical replacement for gulp-util's error handling; this is a routine, expected migration across the gulp ecosystem.	ai	2026/04/23

Versions (showing 49 of 49)

Version	Deps	Published
2.1.0	5 / 5	2017-12-29
2.0.4	5 / 4	2016-11-14
2.0.3	5 / 4	2016-11-13
2.0.2	5 / 3	2016-10-24
2.0.1	5 / 3	2016-05-09
2.0.0	5 / 3	2015-11-19
1.12.0	6 / 3	2015-10-29
1.11.2	6 / 3	2015-07-02
1.11.1	6 / 3	2015-06-29
1.11.0	6 / 3	2015-05-22
1.10.0	6 / 3	2015-04-01
1.9.4	6 / 3	2015-03-18
1.9.3	6 / 3	2015-03-18
1.9.2	6 / 3	2015-02-02
1.9.0	6 / 3	2014-11-03
1.8.6	6 / 3	2014-10-28
1.8.5	6 / 3	2014-09-27
1.8.4	6 / 3	2014-08-04
1.8.3	6 / 3	2014-08-01
1.8.2	6 / 3	2014-07-30
1.8.1	6 / 3	2014-07-29
1.8.0	6 / 3	2014-07-25
1.7.1	6 / 3	2014-07-11
1.7.0	6 / 3	2014-07-08
1.6.4	6 / 3	2014-07-01
1.6.3	6 / 3	2014-06-16
1.6.2	6 / 3	2014-06-04
1.6.1	6 / 3	2014-05-15
1.6.0	6 / 3	2014-05-15
1.5.6	6 / 3	2014-05-15
1.5.5	5 / 2	2014-04-24
1.5.4	7 / 2	2014-04-23
1.5.3	7 / 2	2014-04-02
1.5.2	7 / 2	2014-03-31
1.5.1	5 / 2	2014-03-23
1.5.0	4 / 2	2014-02-24
1.4.2	4 / 2	2014-02-12
1.4.1	4 / 2	2014-02-12
1.4.0	3 / 2	2014-02-06
1.3.4	3 / 2	2014-01-03
1.3.3	2 / 3	2013-12-31
1.3.2	2 / 3	2013-12-11
1.3.1	2 / 3	2013-12-10
1.3.0	2 / 3	2013-12-08
1.2.0	2 / 3	2013-12-08
1.1.0	2 / 2	2013-12-01
1.0.0	2 / 2	2013-11-11
0.1.0	2 / 2	2013-10-28
0.0.1	3 / 2	2013-08-08

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: contra → spalger (on 2016-11-14) provenance

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

v2.0.3

2 findings

HIGH Publisher changed: spalger → contra (on 2016-11-13) provenance

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

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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

v1.12.0

1 finding

LOW No provenance attestation provenance

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

v1.11.2

1 finding

LOW No provenance attestation provenance

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

v1.11.1

1 finding

LOW No provenance attestation provenance

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

v1.11.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: spenceralger → spalger (on 2015-05-22) provenance

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

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.4

1 finding

LOW No provenance attestation provenance

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

v1.9.3

1 finding

LOW No provenance attestation provenance

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

v1.9.2

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.6

1 finding

LOW No provenance attestation provenance

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

v1.8.5

1 finding

LOW No provenance attestation provenance

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

v1.8.4

1 finding

LOW No provenance attestation provenance

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

v1.8.3

1 finding

LOW No provenance attestation provenance

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

v1.8.2

1 finding

LOW No provenance attestation provenance

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

v1.8.1

1 finding

LOW No provenance attestation provenance

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

v1.8.0

1 finding

LOW No provenance attestation provenance

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

v1.7.1

1 finding

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.4

1 finding

LOW No provenance attestation provenance

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

v1.6.3

1 finding

LOW No provenance attestation provenance

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

v1.6.2

1 finding

LOW No provenance attestation provenance

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

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.6

1 finding

LOW No provenance attestation provenance

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

v1.5.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: fractal → spenceralger (on 2014-04-24) provenance

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

v1.5.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: spenceralger → fractal (on 2014-04-23) provenance

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

v1.5.3

1 finding

LOW No provenance attestation provenance

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

v1.5.2

1 finding

LOW No provenance attestation provenance

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

v1.5.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: fractal → spenceralger (on 2014-03-23) provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.2

1 finding

LOW No provenance attestation provenance

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

v1.4.1

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.4

1 finding

LOW No provenance attestation provenance

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

v1.3.3

1 finding

LOW No provenance attestation provenance

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

v1.3.2

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

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