commander 2.12.0
the complete solution for node.js command-line programs
commander@2.12.0 was published on 2017-11-22. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
All commander versions · Permanent reference to 2.12.0 · Latest release
Package specifications
| Version | 2.12.0 |
|---|---|
| License declaration | MIT |
| Published | 2017-11-22T23:04:54.032Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| 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 | index |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 1 |
| Repository stars | 28438 |
| Repository forks | 1790 |
Install commander 2.12.0
npm install commander@2.12.0 pnpm add commander@2.12.0 yarn add commander@2.12.0
Runtime dependencies
- @types/node ^7.0.48
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.
- @types/node@7.10.14 — 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.
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
|---|---|
| Code-Review | 9/10 — Found 20/22 approved changesets -- score normalized to 9 |
| Security-Policy | 10/10 — security policy file detected |
| Maintained | 9/10 — 1 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 9 |
| Token-Permissions | 9/10 — detected GitHub workflow tokens with excessive permissions |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Pinned-Dependencies | 10/10 — all dependencies are pinned |
| 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 |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 8/10 — SAST tool detected but not run on all commits |
Evidence and freshness
- https://registry.npmjs.org/commander/2.12.0 — retrieved 2026-10-29T07:09:33.809Z
- https://api.deps.dev/v3/projects/github.com%2Ftj%2Fcommander.js — retrieved 2026-10-29T05:55:24.596Z
- https://api.deps.dev/v3/systems/npm/packages/commander/versions/2.12.0 — retrieved 2026-10-29T07:09:34.368Z
- https://api.deps.dev/v3/systems/npm/packages/commander/versions/2.12.0:dependencies — retrieved 2026-10-29T07:09:34.381Z