← Home

grunt-sails-linker

npm Repository Homepage

Autoinsert script and link tags in an html file.

13
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

zolmeisterbalderdashymikermcneil

Keywords

gruntpluginsailslinker

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from zolmeister to balderdashy occurred in 2013 as a legitimate transfer to the Sails.js org. This is stable historical context, not a compromise signal. ai
maintainer-change maintainer-added AI (maintainer-change): balderdashy was added as maintainer in 2013 as part of the legitimate Sails.js org adoption of this grunt plugin. No ongoing risk. ai

Versions (showing 13 of 13)

Version Deps Published
1.0.4 0 / 4
1.0.3 0 / 4
1.0.2 0 / 4
1.0.1 0 / 4
1.0.0 0 / 4
0.10.1 0 / 4
0.9.6 0 / 4
0.9.5 0 / 4
0.9.4 0 / 4
0.9.3 0 / 4
0.9.2 0 / 4
0.9.0 0 / 4
0.2.0 0 / 4

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

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.

v0.10.1

2 findings
HIGH Publisher changed: balderdashy → mikermcneil (on 2015-01-19) provenance

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

2 findings
HIGH Publisher changed: balderdashy → zolmeister (on 2015-01-15) provenance

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

1 finding
LOW No provenance attestation provenance

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

v0.9.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: zolmeister → balderdashy (on 2013-10-31) provenance

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

v0.9.3

1 finding
LOW No provenance attestation provenance

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

v0.9.2

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
HIGH Publisher changed: zolmeister → balderdashy (on 2013-07-18) provenance

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