grunt-jasmine-node-coverage 0.2.0

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

grunt-jasmine-node-coverage@0.2.0 was published on 2014-11-03. Its manifest declares 2 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.8.0.

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

Package specifications

Version	0.2.0
License declaration	Not declared
Published	2014-11-03T16:27:08.866Z
Node.js requirement	>=0.8.0
Type declarations	Not declared
Runtime dependency count	2
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	grunt.js
Side effects declaration	Not declared
Direct advisories	0
Resolved graph dependencies	61
Repository stars	26
Repository forks	23

Install grunt-jasmine-node-coverage 0.2.0

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

Runtime dependencies

jasmine-node >=1.4.0
istanbul ~0.3

Peer requirements

grunt ~0.4

Optional dependencies

None declared

Resolved dependency graph

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

istanbul@0.3.22 — direct
jasmine-node@3.0.0 — direct
abbrev@1.0.9 — indirect
async@1.5.2 — indirect
escodegen@1.7.1 — indirect
esprima@2.5.0 — indirect
fileset@0.2.1 — indirect
handlebars@4.7.10 — indirect
js-yaml@3.15.2 — indirect
mkdirp@0.5.6 — indirect
nopt@3.0.6 — indirect
once@1.4.0 — indirect
resolve@1.1.7 — indirect
supports-color@3.2.3 — indirect
which@1.3.1 — indirect
wordwrap@1.0.0 — indirect
coffeescript@1.12.7 — indirect
gaze@1.1.3 — indirect
jasmine-growl-reporter@2.0.0 — indirect
jasmine-reporters@1.0.2 — indirect
mkdirp@0.3.5 — indirect
requirejs@2.3.8 — indirect
underscore@1.9.2 — indirect
walkdir@0.0.12 — indirect
esprima@1.2.5 — indirect
estraverse@1.9.3 — indirect
esutils@2.0.3 — indirect
optionator@0.5.0 — indirect
source-map@0.2.0 — indirect
glob@5.0.15 — indirect
minimatch@2.0.10 — indirect
minimist@1.2.8 — indirect
neo-async@2.6.2 — indirect
source-map@0.6.1 — indirect
uglify-js@3.19.3 — indirect
argparse@1.0.10 — indirect
esprima@4.0.1 — indirect
wrappy@1.0.2 — indirect
has-flag@1.0.0 — indirect
isexe@2.0.0 — indirect
globule@1.3.4 — indirect
growl@1.10.5 — indirect
mkdirp@0.3.5 — indirect
deep-is@0.1.4 — indirect
fast-levenshtein@1.0.7 — indirect
levn@0.2.5 — indirect
prelude-ls@1.1.2 — indirect
type-check@0.3.2 — indirect
wordwrap@0.0.3 — indirect
amdefine@1.0.1 — indirect
inflight@1.0.6 — indirect
inherits@2.0.4 — indirect
path-is-absolute@1.0.1 — indirect
brace-expansion@1.1.21 — indirect
sprintf-js@1.0.3 — indirect
glob@7.1.7 — indirect
lodash@4.18.1 — indirect
minimatch@3.0.8 — indirect
balanced-match@1.0.2 — indirect
concat-map@0.0.1 — indirect
fs.realpath@1.0.0 — 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/0.2.0 — retrieved 2026-10-30T15:06:30.723Z
https://api.deps.dev/v3/systems/npm/packages/grunt-jasmine-node-coverage/versions/0.2.0 — retrieved 2026-10-30T15:06:31.241Z
https://api.deps.dev/v3/systems/npm/packages/grunt-jasmine-node-coverage/versions/0.2.0:dependencies — retrieved 2026-10-30T15:06:31.267Z
https://api.deps.dev/v3/projects/github.com%2Fjribble%2Fgrunt-jasmine-node-coverage — retrieved 2026-10-30T15:06:31.897Z