terminal-kit 0.5.4
Terminal utilities with support for colors (even 256 colors or 24 bits), styles, inputs, mouse and many more...
terminal-kit@0.5.4 was published on 2014-11-15. 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 terminal-kit versions · Permanent reference to 0.5.4 · Latest release
Package specifications
| Version | 0.5.4 |
|---|---|
| License declaration | MIT |
| Published | 2014-11-15T18:14:28.858Z |
| 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 | lib/terminal.js |
| Side effects declaration | Not declared |
| Direct advisories | 1 |
| Resolved graph dependencies | 4 |
| Repository stars | 3379 |
| Repository forks | 206 |
Install terminal-kit 0.5.4
npm install terminal-kit@0.5.4 pnpm add terminal-kit@0.5.4 yarn add terminal-kit@0.5.4
Runtime dependencies
- tree-kit ^0.3.1
- async-kit ^0.5.5
- string-kit ^0.0.18
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.
- async-kit@0.5.10 — direct
- string-kit@0.0.18 — direct
- tree-kit@0.3.6 — direct
- tree-kit@0.5.27 — 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.
Known direct advisories
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Security-Policy | 4/10 — security policy file detected |
|---|---|
| Code-Review | 0/10 — Found 2/28 approved changesets -- score normalized to 0 |
| Maintained | 4/10 — 4 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 4 |
| 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 |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Fuzzing | 0/10 — project is not fuzzed |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/terminal-kit/0.5.4 — retrieved 2026-10-31T06:28:50.332Z
- https://api.deps.dev/v3/systems/npm/packages/terminal-kit/versions/0.5.4 — retrieved 2026-10-31T06:28:50.699Z
- https://api.deps.dev/v3/systems/npm/packages/terminal-kit/versions/0.5.4:dependencies — retrieved 2026-10-31T06:28:50.723Z
- https://api.deps.dev/v3/projects/github.com%2Fcronvel%2Fterminal-kit — retrieved 2026-10-31T06:28:51.117Z