grunt-timer 0.0.1
Time the execution of each of your grunt tasks automatically, calculates a total execution time and outputs to the console.
grunt-timer@0.0.1 was published on 2013-08-20. Its manifest declares 5 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.8.x.
All grunt-timer versions · Permanent reference to 0.0.1 · Latest release
Package specifications
| Version | 0.0.1 |
|---|---|
| License declaration | Not declared |
| Published | 2013-08-20T10:48:48.831Z |
| Node.js requirement | >= 0.8.x |
| Type declarations | Not declared |
| Runtime dependency count | 5 |
| Peer requirement count | 0 |
| 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-timer.min.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 70 |
| Repository stars | 14 |
| Repository forks | 7 |
Install grunt-timer 0.0.1
npm install grunt-timer@0.0.1 pnpm add grunt-timer@0.0.1 yarn add grunt-timer@0.0.1
Runtime dependencies
- grunt ~0.4.1
- grunt-contrib-watch ~0.5.2
- grunt-contrib-jshint ~0.6.3
- grunt-contrib-uglify ~0.2.2
- duration ~0.1.4
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- duration@0.1.4 — direct
- grunt@0.4.5 — direct
- grunt-contrib-jshint@0.6.5 — direct
- grunt-contrib-uglify@0.2.7 — direct
- grunt-contrib-watch@0.5.3 — direct
- es5-ext@0.9.2 — indirect
- async@0.1.22 — indirect
- coffee-script@1.3.3 — indirect
- colors@0.6.2 — indirect
- dateformat@1.0.2-1.2.3 — indirect
- eventemitter2@0.4.14 — indirect
- exit@0.1.2 — indirect
- findup-sync@0.1.3 — indirect
- getobject@0.1.0 — indirect
- glob@3.1.21 — indirect
- grunt-legacy-log@0.1.3 — indirect
- grunt-legacy-util@0.2.0 — indirect
- hooker@0.2.3 — indirect
- iconv-lite@0.2.11 — indirect
- js-yaml@2.0.5 — indirect
- lodash@0.9.2 — indirect
- minimatch@0.2.14 — indirect
- nopt@1.0.10 — indirect
- rimraf@2.2.8 — indirect
- underscore.string@2.2.1 — indirect
- which@1.0.9 — indirect
- jshint@2.1.11 — indirect
- grunt-lib-contrib@0.6.1 — indirect
- uglify-js@2.4.24 — indirect
- gaze@0.4.3 — indirect
- tiny-lr@0.0.4 — indirect
- glob@3.2.11 — indirect
- lodash@2.4.2 — indirect
- graceful-fs@1.2.3 — indirect
- inherits@1.0.2 — indirect
- grunt-legacy-log-utils@0.1.1 — indirect
- lodash@2.4.2 — indirect
- underscore.string@2.3.3 — indirect
- argparse@0.1.16 — indirect
- esprima@1.0.4 — indirect
- lru-cache@2.7.3 — indirect
- sigmund@1.0.1 — indirect
- abbrev@1.1.1 — indirect
- cli@0.4.5 — indirect
- console-browserify@0.1.6 — indirect
- shelljs@0.1.4 — indirect
- underscore@1.4.4 — indirect
- zlib-browserify@0.0.1 — indirect
- async@0.2.10 — indirect
- source-map@0.1.34 — indirect
- uglify-to-browserify@1.0.2 — indirect
- yargs@3.5.4 — indirect
- globule@0.1.0 — indirect
- debug@0.7.4 — indirect
- faye-websocket@0.4.4 — indirect
- noptify@0.0.3 — indirect
- qs@0.5.6 — indirect
- inherits@2.0.4 — indirect
- minimatch@0.3.0 — indirect
- lodash@2.4.2 — indirect
- underscore.string@2.3.3 — indirect
- underscore@1.7.0 — indirect
- underscore.string@2.4.0 — indirect
- amdefine@1.0.1 — indirect
- camelcase@1.2.1 — indirect
- decamelize@1.2.0 — indirect
- window-size@0.1.0 — indirect
- wordwrap@0.0.2 — indirect
- lodash@1.0.2 — indirect
- nopt@2.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 | 0/10 — Found 2/29 approved changesets -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| 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 | 0/10 — license file not 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-timer/0.0.1 — retrieved 2026-10-30T18:26:42.170Z
- https://api.deps.dev/v3/projects/github.com%2Fleecrossley%2Fgrunt-timer — retrieved 2026-10-30T14:06:00.878Z
- https://api.deps.dev/v3/systems/npm/packages/grunt-timer/versions/0.0.1 — retrieved 2026-10-30T18:26:42.664Z
- https://api.deps.dev/v3/systems/npm/packages/grunt-timer/versions/0.0.1:dependencies — retrieved 2026-10-30T18:26:42.874Z