complexity-report 0.2.2
A tool for reporting code complexity metrics in JavaScript projects.
complexity-report@0.2.2 was published on 2012-10-28. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All complexity-report versions · Permanent reference to 0.2.2 · Latest release
Package specifications
| Version | 0.2.2 |
|---|---|
| License declaration | MIT |
| Published | 2012-10-28T01:38:32.868Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| 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 | ./src/complexityReport.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 4 |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install complexity-report 0.2.2
npm install complexity-report@0.2.2 pnpm add complexity-report@0.2.2 yarn add complexity-report@0.2.2
Runtime dependencies
- check-types 0.2.x
- esprima 0.9.x
- commander 1.0.5
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.
- check-types@0.2.5 — direct
- commander@1.0.5 — direct
- esprima@0.9.9 — direct
- keypress@0.1.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.
Evidence and freshness
- https://registry.npmjs.org/complexity-report/0.2.2 — retrieved 2026-10-30T14:45:03.363Z
- https://api.deps.dev/v3/systems/npm/packages/complexity-report/versions/0.2.2 — retrieved 2026-10-30T14:45:03.842Z
- https://api.deps.dev/v3/systems/npm/packages/complexity-report/versions/0.2.2:dependencies — retrieved 2026-10-30T14:45:03.869Z