verb-tag-jscomments
Tag for Verb. Uses js-comments to parse JavaScript code comments and generate API documentation.
verb-tag-jscomments@0.2.2 was published on 2014-08-25. Its manifest declares 3 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 verb-tag-jscomments versions · Permanent reference to 0.2.2
Package specifications
| Version | 0.2.2 |
|---|---|
| License declaration | Not declared |
| Published | 2014-08-25T21:23:11.526Z |
| Node.js requirement | >=0.10.0 |
| 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 | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 67 |
| Repository stars | 3 |
| Repository forks | 0 |
Install verb-tag-jscomments 0.2.2
npm install verb-tag-jscomments@0.2.2 pnpm add verb-tag-jscomments@0.2.2 yarn add verb-tag-jscomments@0.2.2
Runtime dependencies
- fs-utils ^0.4.3
- js-comments ^0.3.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.
- fs-utils@0.4.3 — direct
- js-comments@0.3.9 — direct
- lodash@2.4.2 — direct
- async@0.6.2 — indirect
- globule@0.2.0 — indirect
- graceful-fs@2.0.3 — indirect
- js-yaml@3.0.2 — indirect
- mkdirp@0.3.5 — indirect
- rimraf@2.2.8 — indirect
- frep@0.2.3 — indirect
- globby@1.2.0 — indirect
- js-comments-template@0.4.2 — indirect
- lodash@3.10.1 — indirect
- lodash-helpers@0.1.0 — indirect
- parse-comments@0.3.4 — indirect
- relative@1.2.0 — indirect
- repeat-string@1.6.1 — indirect
- glob@3.2.11 — indirect
- minimatch@0.2.14 — indirect
- argparse@0.1.16 — indirect
- esprima@1.0.4 — indirect
- replacements@0.1.3 — indirect
- array-union@1.0.2 — indirect
- async@0.9.2 — indirect
- glob@4.5.3 — indirect
- object-assign@2.1.1 — indirect
- chalk@0.5.1 — indirect
- arrayify-compact@0.1.1 — indirect
- code-context@0.2.3 — indirect
- gfm-code-blocks@0.2.2 — indirect
- inflection@1.13.4 — indirect
- inherits@2.0.4 — indirect
- minimatch@0.3.0 — indirect
- lru-cache@2.7.3 — indirect
- sigmund@1.0.1 — indirect
- underscore@1.7.0 — indirect
- underscore.string@2.4.0 — indirect
- array-uniq@1.0.3 — indirect
- inflight@1.0.6 — indirect
- minimatch@2.0.10 — indirect
- once@1.4.0 — indirect
- ansi-styles@1.1.0 — indirect
- escape-string-regexp@1.0.5 — indirect
- has-ansi@0.1.0 — indirect
- strip-ansi@0.3.0 — indirect
- supports-color@0.2.0 — indirect
- array-flatten@2.1.2 — indirect
- extract-comments@0.4.2 — indirect
- gfm-code-block-regex@0.2.3 — indirect
- wrappy@1.0.2 — indirect
- brace-expansion@1.1.21 — indirect
- ansi-regex@0.2.1 — indirect
- line-count@0.1.0 — indirect
- map-files@0.1.2 — indirect
- mixin-deep@0.1.0 — indirect
- balanced-match@1.0.2 — indirect
- concat-map@0.0.1 — indirect
- globby@0.1.1 — indirect
- for-own@0.1.5 — indirect
- is-plain-object@0.1.0 — indirect
- array-differ@0.1.0 — indirect
- array-union@0.1.0 — indirect
- async@0.9.2 — indirect
- glob@4.5.3 — indirect
- for-in@1.0.2 — indirect
- array-uniq@0.1.1 — indirect
- minimatch@2.0.10 — 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.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| SAST | 0/10 — no SAST tool detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Code-Review | 0/10 — Found 0/8 approved changesets -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge 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 |
| Security-Policy | 0/10 — security policy file not detected |
Evidence and freshness
- https://registry.npmjs.org/verb-tag-jscomments/0.2.2 — retrieved 2026-10-29T22:11:43.048Z
- https://api.deps.dev/v3/systems/npm/packages/verb-tag-jscomments/versions/0.2.2 — retrieved 2026-10-29T22:11:43.577Z
- https://api.deps.dev/v3/systems/npm/packages/verb-tag-jscomments/versions/0.2.2:dependencies — retrieved 2026-10-29T22:11:43.585Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fverb-tag-jscomments — retrieved 2026-10-29T22:11:43.814Z