parse-comments 0.1.2
Parse JavaScript comments, or comments using a similar format.
parse-comments@0.1.2 was published on 2014-08-09. 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.10.0.
All parse-comments versions · Permanent reference to 0.1.2 · Latest release
Package specifications
| Version | 0.1.2 |
|---|---|
| License declaration | Not declared |
| Published | 2014-08-09T20:28:46.003Z |
| Node.js requirement | >=0.10.0 |
| 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 | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | 67 |
| Repository forks | 22 |
Install parse-comments 0.1.2
npm install parse-comments@0.1.2 pnpm add parse-comments@0.1.2 yarn add parse-comments@0.1.2
Runtime dependencies
- arrayify-compact ^0.1.0
- code-context ^0.1.1
- count-lines ^0.1.2
- extract-range ^0.1.0
- lodash ^2.4.1
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.
- array-flatten@2.1.2 — indirect
- arrayify-compact@0.1.1 — direct
- code-context@0.1.1 — direct
- count-lines@0.1.2 — direct
- extract-range@0.1.0 — direct
- lodash@2.4.2 — 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.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Code-Review | 0/10 — Found 0/4 approved changesets -- 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 |
| License | 10/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Security-Policy | 0/10 — security policy 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/parse-comments/0.1.2 — retrieved 2026-10-29T22:39:18.920Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fparse-comments — retrieved 2026-10-29T22:05:13.587Z
- https://api.deps.dev/v3/systems/npm/packages/parse-comments/versions/0.1.2:dependencies — retrieved 2026-10-29T22:39:19.440Z
- https://api.deps.dev/v3/systems/npm/packages/parse-comments/versions/0.1.2 — retrieved 2026-10-29T22:39:19.418Z