complexity-report 1.0.7
Software complexity analysis for JavaScript projects
complexity-report@1.0.7 was published on 2014-12-21. 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 1.0.7 · Latest release
Package specifications
| Version | 1.0.7 |
|---|---|
| License declaration | MIT |
| Published | 2014-12-21T14:20:09.222Z |
| 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 | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 8 |
| Repository stars | 209 |
| Repository forks | 27 |
Install complexity-report 1.0.7
npm install complexity-report@1.0.7 pnpm add complexity-report@1.0.7 yarn add complexity-report@1.0.7
Runtime dependencies
- escomplex-js 0.1.5
- check-types 2.1.x
- commander 2.0.x
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@2.1.1 — direct
- commander@2.0.0 — direct
- escomplex@0.2.6 — indirect
- escomplex-ast-moz@0.1.6 — indirect
- escomplex-js@0.1.5 — direct
- escomplex-traits@0.2.0 — indirect
- esprima@1.0.4 — indirect
- matrix-utilities@1.2.4 — 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/25 approved changesets -- score normalized to 0 |
|---|---|
| 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/complexity-report/1.0.7 — retrieved 2026-10-30T15:49:12.191Z
- https://api.deps.dev/v3/systems/npm/packages/complexity-report/versions/1.0.7 — retrieved 2026-10-30T15:49:12.626Z
- https://api.deps.dev/v3/systems/npm/packages/complexity-report/versions/1.0.7:dependencies — retrieved 2026-10-30T15:49:12.695Z
- https://api.deps.dev/v3/projects/github.com%2Fjared-stilwell%2Fcomplexity-report — retrieved 2026-10-30T15:49:13.181Z