node-pty 0.7.3-beta1

Fork pseudoterminals in Node.JS

node-pty@0.7.3-beta1 was published on 2017-11-11. 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 node-pty versions · Permanent reference to 0.7.3-beta1 · Latest release

Package specifications

Version0.7.3-beta1
License declarationMIT
Published2017-11-11T22:02:19.698Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entry./lib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars2053
Repository forks348

Install node-pty 0.7.3-beta1

npm install node-pty@0.7.3-beta1
pnpm add node-pty@0.7.3-beta1
yarn add node-pty@0.7.3-beta1

Runtime dependencies

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.

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.

Maintained10/10 — 17 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts6/10 — binaries present in source code
Code-Review10/10 — all changesets reviewed
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Security-Policy10/10 — security policy file detected
Pinned-Dependencies8/10 — dependency not pinned by hash detected -- score normalized to 8
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License9/10 — license file detected
Branch-Protection8/10 — branch protection is not maximal on development and all release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness