grunt-jasmine-node-coverage 2.0.0

Grunt task for running jasmine using istanbul for code coverage reports. Based off of grunt-jasmine-node by Omar Gonzalez (s9tpepper).

grunt-jasmine-node-coverage@2.0.0 was published on 2017-09-20. Its manifest declares 5 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=4.2.0.

All grunt-jasmine-node-coverage versions · Permanent reference to 2.0.0 · Latest release

Package specifications

Version	2.0.0
License declaration	MIT
Published	2017-09-20T11:05:56.426Z
Node.js requirement	>=4.2.0
Type declarations	Not declared
Runtime dependency count	5
Peer requirement count	1
Optional dependency count	0
Minified size	Measurement not available yet
Minified + gzip	Measurement not available yet
Unpacked distribution size	Not supplied
Published file count	Not supplied
Package type	Not declared
ES module entry	Not declared
Default entry	tasks/jasmine-node-task.js
Side effects declaration	Not declared
Direct advisories	0
Resolved graph dependencies	54
Repository stars	26
Repository forks	23

Install grunt-jasmine-node-coverage 2.0.0

npm install grunt-jasmine-node-coverage@2.0.0
pnpm add grunt-jasmine-node-coverage@2.0.0
yarn add grunt-jasmine-node-coverage@2.0.0

Runtime dependencies

Peer requirements

grunt >=0.4.5

Optional dependencies

None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

@xmldom/xmldom@0.8.15 — indirect
abbrev@1.0.9 — indirect
amdefine@1.0.1 — indirect
argparse@1.0.10 — indirect
async@1.5.2 — indirect
balanced-match@1.0.2 — indirect
brace-expansion@1.1.21 — indirect
colors@1.1.2 — indirect
concat-map@0.0.1 — indirect
deep-is@0.1.4 — indirect
deepmerge@1.5.2 — direct
escodegen@1.8.1 — indirect
esprima@2.7.3 — indirect
esprima@4.0.1 — indirect
estraverse@1.9.3 — indirect
esutils@2.0.3 — indirect
exit@0.1.2 — indirect
fast-levenshtein@2.0.6 — indirect
fs.realpath@1.0.0 — indirect
glob@5.0.15 — indirect
glob@7.2.3 — indirect
handlebars@4.7.10 — indirect
has-flag@1.0.0 — indirect
inflight@1.0.6 — indirect
inherits@2.0.4 — indirect
isexe@2.0.0 — indirect
istanbul@0.4.5 — direct
jasmine@2.99.0 — direct
jasmine-core@2.99.1 — indirect
jasmine-reporters@2.5.2 — direct
jasmine-spec-reporter@3.3.0 — direct
js-yaml@3.15.2 — indirect
levn@0.3.0 — indirect
minimatch@3.1.5 — indirect
minimist@1.2.8 — indirect
mkdirp@0.5.6 — indirect
mkdirp@1.0.4 — indirect
neo-async@2.6.2 — indirect
nopt@3.0.6 — indirect
once@1.4.0 — indirect
optionator@0.8.3 — indirect
path-is-absolute@1.0.1 — indirect
prelude-ls@1.1.2 — indirect
resolve@1.1.7 — indirect
source-map@0.2.0 — indirect
source-map@0.6.1 — indirect
sprintf-js@1.0.3 — indirect
supports-color@3.2.3 — indirect
type-check@0.3.2 — indirect
uglify-js@3.19.3 — indirect
which@1.3.1 — indirect
word-wrap@1.2.5 — indirect
wordwrap@1.0.0 — indirect
wrappy@1.0.2 — indirect

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review	2/10 — Found 5/18 approved changesets -- score normalized to 2
Maintained	0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Binary-Artifacts	10/10 — no binaries found in the repo
CII-Best-Practices	0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy	0/10 — security policy file not detected
Fuzzing	0/10 — project is not fuzzed
License	10/10 — license file detected
Branch-Protection	0/10 — branch protection not enabled on development/release branches
SAST	0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness

https://registry.npmjs.org/grunt-jasmine-node-coverage/2.0.0 — retrieved 2026-10-30T16:18:11.341Z
https://api.deps.dev/v3/systems/npm/packages/grunt-jasmine-node-coverage/versions/2.0.0 — retrieved 2026-10-30T16:18:11.760Z
https://api.deps.dev/v3/systems/npm/packages/grunt-jasmine-node-coverage/versions/2.0.0:dependencies — retrieved 2026-10-30T16:18:11.801Z
https://api.deps.dev/v3/projects/github.com%2Fjribble%2Fgrunt-jasmine-node-coverage — retrieved 2026-10-30T16:18:12.333Z