readline2 1.0.0
Readline Façade fixing bugs and issues found in releases 0.8 and 0.10
readline2@1.0.0 was published on 2015-07-17. 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 readline2 versions · Permanent reference to 1.0.0 · View npm registry JSON · Latest release
Package specifications
| Version | 1.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2015-07-17T07:03:39.683Z |
| 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 | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 4 |
| Repository stars | 27 |
| Repository forks | 4 |
Install readline2 1.0.0
npm install readline2@1.0.0 pnpm add readline2@1.0.0 yarn add readline2@1.0.0
Runtime dependencies
- code-point-at ^1.0.0
- is-fullwidth-code-point ^1.0.0
- mute-stream ^0.0.4
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.
- code-point-at@1.1.0 — direct
- is-fullwidth-code-point@1.0.0 — direct
- mute-stream@0.0.4 — direct
- number-is-nan@1.0.1 — 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 |
|---|---|
| Security-Policy | 10/10 — security policy file detected |
| Code-Review | 0/10 — Found 2/21 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 |
| 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
- Readable npm registry JSON — retrieved 2026-11-05T08:04:16.840Z
- https://api.deps.dev/v3/systems/npm/packages/readline2/versions/1.0.0 — retrieved 2026-11-05T08:04:16.919Z
- https://api.deps.dev/v3/systems/npm/packages/readline2/versions/1.0.0:dependencies — retrieved 2026-11-05T08:04:16.944Z
- https://api.deps.dev/v3/projects/github.com%2Fsboudrias%2Freadline2 — retrieved 2026-11-04T17:27:12.919Z (stale snapshot; refresh pending)