grunt-contrib-jade — Greenflagged

Compile Jade templates

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

tkellencowboyshamavladikoffsindresorhusjmeas

Keywords

gruntplugin

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 vladikoff to tkellen occurred in Feb 2015; tkellen is a known Grunt core team member with strong track record. Legitimate org-level maintainer transition, stable for this package.	ai	2026/04/24

Versions (showing 19 of 19)

Version	Deps	Published
1.0.0	2 / 6	2016-03-04
0.15.0	2 / 6	2015-07-08
0.14.1	2 / 5	2015-02-02
0.14.0	2 / 5	2014-12-23
0.13.0	2 / 5	2014-09-30
0.12.0	3 / 5	2014-05-30
0.11.0	3 / 5	2014-03-02
0.10.0	4 / 5	2014-02-11
0.9.1	3 / 5	2014-01-04
0.9.0	2 / 5	2013-12-24
0.8.0	2 / 5	2013-07-30
0.7.0	2 / 5	2013-06-07
0.6.0	2 / 5	2013-05-14
0.5.1	2 / 5	2013-05-07
0.5.0	2 / 5	2013-03-07
0.4.0	1 / 5	2013-02-18
0.3.1	2 / 2	2012-10-12
0.3.0	2 / 2	2012-09-24
0.2.0	2 / 2	2012-09-10

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.15.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: tkellen → vladikoff (on 2015-07-08) provenance

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

v0.14.1

2 findings

HIGH Publisher changed: vladikoff → tkellen (on 2015-02-02) provenance

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

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.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: tkellen → vladikoff (on 2014-03-02) provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.1

1 finding

LOW No provenance attestation provenance

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

v0.9.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: shama → tkellen (on 2013-12-24) provenance

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

v0.8.0

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

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: shama → tkellen (on 2013-06-07) provenance

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

v0.6.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: shama → tkellen (on 2013-05-14) provenance

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

v0.5.1

2 findings

HIGH Publisher changed: tkellen → shama (on 2013-05-07) provenance

This version was published by a different npm account than previous versions on 2013-05-07. 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.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: cowboy → tkellen (on 2013-03-07) provenance

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

v0.4.0

2 findings

HIGH Publisher changed: tkellen → cowboy (on 2013-02-18) provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

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