grunt-complexity — Greenflagged

Evaluates code maintainability using Halstead and Cyclomatic metrics.

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

lawsonnhunzaker

Keywords

gruntplugincomplexityhalsteadcyclomatic

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:test/grunt.0.3/node_modules/nodeunit/examples/browser/nodeunit.js	AI (source-diff): This is the well-known nodeunit browser bundle containing the public-domain json2.js polyfill. It is a vendored test dependency, not runtime code, and poses no malware risk.	ai	2026/04/24
source-diff	net-exec-file:test/grunt.0.3/node_modules/nodeunit/deps/json2.js	AI (source-diff): This is the public-domain json2.js JSON polyfill vendored under test dependencies. The 'network calls' are documentation URLs, not actual network activity.	ai	2026/04/24
source-diff	large-new-source-files	AI (source-diff): Size increase is due to bundling full node_modules trees for integration testing (grunt.0.3 and grunt.0.4 test fixtures). Legitimate test infrastructure, not injected payloads.	ai	2026/04/24
source-diff	source-size-tripled	AI (source-diff): 12x size increase is entirely explained by vendored test node_modules (nodeunit, iconv-lite, js-yaml, jquery, etc.). No runtime payload injection.	ai	2026/04/24
source-diff	net-exec-file:test/grunt.0.4/node_modules/findup-sync/node_modules/lodash/vendor/benchmark.js/benchmark.js	AI (source-diff): Legitimate Benchmark.js 1.0.0 vendored in test fixtures; Rhino timer shim triggers rule but is not malware.	ai	2026/04/24
source-diff	net-exec-file:test/grunt.0.4/node_modules/findup-sync/node_modules/lodash/lodash.js	AI (source-diff): Legitimate Lo-Dash 1.0.1 vendored in test fixtures; UMD boilerplate triggers rule but is not malware.	ai	2026/04/24
phantom-deps	phantom-dep:grunt	AI (phantom-deps): grunt is a peer dependency for a grunt plugin; not directly imported by design — stable false positive for this package.	ai	2026/04/24
source-diff	net-exec-file:test/grunt.0.4/node_modules/findup-sync/node_modules/lodash/vendor/qunit-clib/qunit-clib.js	AI (source-diff): Legitimate QUnit CLI Boilerplate vendored in test fixtures; Rhino eval shim triggers rule but is not malware.	ai	2026/04/24
source-diff	net-exec-file:test/grunt.0.4/node_modules/findup-sync/node_modules/lodash/dist/lodash.compat.js	AI (source-diff): Legitimate Lo-Dash 1.0.1 build variant vendored in test fixtures; standard UMD pattern, not malware.	ai	2026/04/24
source-diff	net-exec-file:test/grunt.0.4/node_modules/findup-sync/node_modules/lodash/dist/lodash.js	AI (source-diff): Legitimate Lo-Dash 1.0.1 modern build vendored in test fixtures; standard UMD pattern, not malware.	ai	2026/04/24
source-diff	net-exec-file:test/grunt.0.4/node_modules/findup-sync/node_modules/lodash/dist/lodash.underscore.js	AI (source-diff): Legitimate Lo-Dash 1.0.1 underscore build vendored in test fixtures; standard UMD pattern, not malware.	ai	2026/04/24

Versions (showing 23 of 23)

Version	Deps	Published
1.1.0	4 / 7	2017-05-10
1.0.1	4 / 7	2016-08-25
1.0.0	4 / 7	2016-08-18
0.4.0	3 / 7	2016-08-18
0.3.1	3 / 7	2016-08-18
0.3.0	3 / 7	2015-01-20
0.2.0	3 / 7	2014-06-23
0.1.71	3 / 6	2014-06-12
0.1.51	2 / 6	2014-03-31
0.1.7	3 / 6	2014-05-29
0.1.6	3 / 6	2014-04-24
0.1.5	2 / 6	2014-03-31
0.1.4	2 / 5	2013-12-30
0.1.3	2 / 5	2013-06-06
0.1.2	2 / 5	2013-04-08
0.1.0	2 / 1	2013-02-23
0.0.7	2 / 1	2013-02-19
0.0.6	2 / 1	2013-01-15
0.0.5	2 / 1	2013-01-14
0.0.4	2 / 1	2013-01-14
0.0.3	2 / 1	2013-01-14
0.0.2	2 / 0	2013-01-13
0.0.1	2 / 0	2013-01-13

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

1 finding

LOW No provenance attestation provenance

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

v0.1.51

1 finding

LOW No provenance attestation provenance

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

v0.1.7

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

7 findings

HIGH New file with network + code execution: test/grunt.0.4/node_modules/findup-sync/node_modules/lodash/lodash.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: test/grunt.0.4/node_modules/findup-sync/node_modules/lodash/dist/lodash.compat.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: test/grunt.0.4/node_modules/findup-sync/node_modules/lodash/dist/lodash.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: test/grunt.0.4/node_modules/findup-sync/node_modules/lodash/dist/lodash.underscore.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: test/grunt.0.4/node_modules/findup-sync/node_modules/lodash/vendor/benchmark.js/benchmark.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: test/grunt.0.4/node_modules/findup-sync/node_modules/lodash/vendor/qunit-clib/qunit-clib.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.1.0

3 findings

HIGH New file with network + code execution: test/grunt.0.3/node_modules/nodeunit/examples/browser/nodeunit.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: test/grunt.0.3/node_modules/nodeunit/deps/json2.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.0.7

3 findings

HIGH New file with network + code execution: test/grunt.0.3/node_modules/nodeunit/examples/browser/nodeunit.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: test/grunt.0.3/node_modules/nodeunit/deps/json2.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.0.6

1 finding

LOW No provenance attestation provenance

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

v0.0.5

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.3

1 finding

LOW No provenance attestation provenance

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

v0.0.2

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