cjson
cjson - Commented JavaScript Object Notation. It is a json loader, which parses only valid json files, but with comments enabled. Useful for loading configs.
cjson@0.5.0 was published on 2017-01-07. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.3.0.
All cjson versions · Permanent reference to 0.5.0
Package specifications
| Version | 0.5.0 |
|---|---|
| License declaration | MIT |
| Published | 2017-01-07T19:03:10.569Z |
| Node.js requirement | >= 0.3.0 |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| 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 | 2 |
| Repository stars | 61 |
| Repository forks | 15 |
Install cjson 0.5.0
npm install cjson@0.5.0 pnpm add cjson@0.5.0 yarn add cjson@0.5.0
Runtime dependencies
- json-parse-helpfulerror ^1.0.3
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.
- jju@1.4.0 — indirect
- json-parse-helpfulerror@1.0.3 — direct
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 | 3/10 — Found 10/27 approved changesets -- score normalized to 3 |
|---|---|
| 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/cjson/0.5.0 — retrieved 2026-10-29T12:03:07.769Z
- https://api.deps.dev/v3/systems/npm/packages/cjson/versions/0.5.0 — retrieved 2026-10-29T12:03:08.250Z
- https://api.deps.dev/v3/systems/npm/packages/cjson/versions/0.5.0:dependencies — retrieved 2026-10-29T12:03:08.300Z
- https://api.deps.dev/v3/projects/github.com%2Fkof%2Fnode-cjson — retrieved 2026-10-29T12:03:08.420Z