← Home

grunt-env

npm Repository Homepage
11
Versions
—
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

jsoversonstephane.bachelier

Keywords

gruntpluginenvconfig

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
license uncommon-license:Apache2 AI (license): Apache 2.0 is a well-known permissive open-source license; the 'uncommon' flag is a false positive for this package. ai
maintainer-change maintainer-added AI (maintainer-change): Same decade-old maintainer transition; stephane.bachelier has been the maintainer since 2014 with a clean history. ai
publish-pattern new-deps-added AI (publish-pattern): ini and lodash are well-established packages consistent with grunt-env's purpose of parsing ENV config files. No malicious signal. ai
source-diff source-size-tripled AI (source-diff): Size increase from 1KB to 8KB is explained by addition of ini parsing and lodash utility functionality; no obfuscation or payload indicators. ai
provenance publisher-changed AI (provenance): Publisher change from jsoverson to stephane.bachelier occurred in 2014 (~10 years ago); new publisher has clean track record (7 approved, 0 rejected). Stable historical transition. ai
phantom-deps phantom-dep:grunt-cli AI (phantom-deps): grunt-cli is a build-time dependency referenced in Gruntfile config, not source imports. ai
phantom-deps phantom-dep:grunt-contrib-clean AI (phantom-deps): Grunt task dependency referenced in config; standard pattern for Grunt plugins. ai
phantom-deps phantom-dep:grunt AI (phantom-deps): Grunt plugins legitimately reference grunt in config; not directly imported in source code. ai

Versions (showing 11 of 11)

Version Deps Published
1.0.1 2 / 3
1.0.0 5 / 0
0.4.4 2 / 4
0.4.3 2 / 4
0.4.2 2 / 3
0.4.1 2 / 3
0.4.0 1 / 3
0.3.0 1 / 2
0.2.1 0 / 2
0.2.0 0 / 2
0.1.0 0 / 1

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

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.

v0.4.4

2 findings
HIGH Publisher changed: jsoverson → stephane.bachelier (on 2015-02-20) provenance

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

2 findings
HIGH Publisher changed: jsoverson → stephane.bachelier (on 2015-02-20) provenance

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

2 findings
HIGH Publisher changed: jsoverson → stephane.bachelier (on 2014-10-02) provenance

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

1 finding
LOW No provenance attestation provenance

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

v0.4.0

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

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.

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.