grunt-contrib-yuidoc MIT 15 versions

grunt-contrib-yuidoc

npm Repository Homepage

Compile YUIDoc Documentation

15

Versions

MIT

License

No

Install Scripts

Missing

Provenance

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): The tkellen→cowboy transition in 2013 is a historical Grunt team handoff; both are known core contributors. This is a stable false positive for this package.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): shama is a recognized Grunt contributor; this 2013-era maintainer addition is a legitimate team expansion, not a compromise signal.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package predates Sigstore by nearly a decade; lack of provenance attestation is expected and not a risk signal for this package.	ai	2026/04/24

Versions (showing 15 of 15)

Version	Deps	Published
1.0.0	1 / 6	2016-03-04
0.10.0	1 / 6	2015-08-24
0.9.0	1 / 6	2015-07-29
0.8.0	1 / 6	2015-05-11
0.7.0	1 / 6	2015-01-21
0.6.0	1 / 6	2014-12-28
0.5.2	1 / 6	2014-03-12
0.5.1	1 / 5	2014-02-24
0.5.0	1 / 5	2013-09-01
0.4.0	1 / 5	2013-02-18
0.3.2	2 / 2	2012-10-12
0.3.1	2 / 2	2012-10-01
0.3.0	2 / 2	2012-09-24
0.2.0	2 / 2	2012-09-10
0.1.0	2 / 2	2012-09-07

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

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

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

LOW No provenance attestation provenance

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

v0.6.0

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

2 findings

HIGH Publisher changed: shama → vladikoff (on 2014-03-12) provenance

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

2 findings

HIGH Publisher changed: shama → vladikoff (on 2014-02-24) provenance

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

HIGH Publisher changed: tkellen → shama (on 2013-09-01) provenance

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

1 finding

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. 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. Only ~12% of npm packages have provenance, so this is common but not ideal.