zigpty
npmv0.2.1Tiny, cross-platform PTY library for Node.js, built in Zig, also usable as a standalone Zig package. Supports Linux, macOS, Android and Windows (via ConPTY).
Not recommended for new projects
No — zigpty should not be adopted for new projects. No license declared — you have no explicit right to use this code.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- AMaintenance: grade A, Excellent.
Last published 79 days ago. 15 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 412 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- FLicense: grade F, Failing.
No license declared — you have no explicit right to use this code.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding zigpty to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- No constraint declared
- Module format
- ESM only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the zigpty README.
import { spawn } from "zigpty";
// auto-detects default shell ($SHELL on Unix, %COMSPEC% on Windows)
const pty = spawn(undefined, [], {
cols: 80,
rows: 24,
terminal: {
data(terminal, data: Uint8Array) {
process.stdout.write(data);
},
},
onExit(exitCode, signal) {
console.log("exited:", exitCode);
},Dependencies
Declared by zigpty v0.2.1. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (7)
Used by
Popular packages that depend on zigpty.
Relationship graph
Dependencies (left) and dependents (right) of zigpty.
Frequently installed together
Framework for building one portable devtool integration that runs in any viewer.
Native-ESM powered web dev build tool
TypeScript definitions for node
Minimal H(TTP) framework built for high performance and portability.
Universal filesystem path utils
Get an available TCP port to listen
Next generation testing framework powered by Vite
Simple yet powerful framework for building command-line apps.
Missing ECMAScript module utils for Node.js
A faster, secure and convenient alternative for JSON.parse
The modular and type safe schema library for validating structural data
Cybernetically enhanced web apps
Release history
15 releases in the last two years, typically about 0 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 0.2.1latest | 2 months ago | 412 KB | — |
| 0.2.0 | 3 months ago | 409 KB | — |
| 0.1.6 | 5 months ago | 334 KB | — |
| 0.1.5 | 5 months ago | 248 KB | — |
| 0.1.4 | 5 months ago | 247 KB | — |
| 0.1.3 | 5 months ago | 247 KB | — |
| 0.1.2 | 5 months ago | 247 KB | — |
| 0.1.1 | 5 months ago | 246 KB | — |
| 0.1.0 | 5 months ago | 242 KB | — |
| 0.0.7 | 5 months ago | 242 KB | — |
| 0.0.6 | 5 months ago | 231 KB | — |
| 0.0.4 | 5 months ago | 229 KB | — |
| 0.0.3 | 5 months ago | 229 KB | — |
| 0.0.2 | 5 months ago | 172 KB | — |
| 0.0.0 | 5 months ago | 45 B | — |
Overview
zigpty is an npm package that tiny, cross-platform PTY library for Node.js, built in Zig, also usable as a standalone Zig package. Supports Linux, macOS, Android and Windows (via ConPTY). It has 2 known dependents in the graph. The latest version is 0.2.1.
Who should use it
Teams working in the npm ecosystem who need tiny, cross-platform PTY library for Node.js, built in Zig, also usable as a standalone Zig package. Supports Linux, macOS, Android and Windows (via ConPTY) and value a focused solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Actively published to the registry.
Cons
- No bundled TypeScript types (may require a separate @types package).
- No license detected — review usage terms before adopting.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use zigpty?
No — zigpty should not be adopted for new projects. No license declared — you have no explicit right to use this code.
How do I install zigpty?
Run `npm install zigpty` to add zigpty to your npm project.
What license is zigpty released under?
No license was detected in zigpty's metadata; review the repository before use.
How popular is zigpty?
npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on zigpty.
Is zigpty still maintained?
The most recent release of zigpty (v0.2.1) was published 2 months ago.
Does zigpty run install scripts?
No. zigpty does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.