@xterm/xterm 6.1.0-beta.331

Full xterm terminal, in your browser

@xterm/xterm@6.1.0-beta.331 was published on 2026-10-29. Its manifest declares 0 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @xterm/xterm versions · Permanent reference to 6.1.0-beta.331 · Latest release

Package specifications

Version6.1.0-beta.331
License declarationMIT
Published2026-10-29T15:13:44.317Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size4630.15 KiB
Published file count122
Package typeNot declared
ES module entrylib/xterm.mjs
Default entrylib/xterm.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars21296
Repository forks2027

Install @xterm/xterm 6.1.0-beta.331

npm install @xterm/xterm@6.1.0-beta.331
pnpm add @xterm/xterm@6.1.0-beta.331
yarn add @xterm/xterm@6.1.0-beta.331

Runtime dependencies

  • None declared

Peer requirements

  • None declared

Optional dependencies

  • None declared

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 — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Code-Review4/10 — Found 4/10 approved changesets -- score normalized to 4
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions9/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
Security-Policy0/10 — security policy file not detected
Pinned-Dependencies10/10 — all dependencies are pinned
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
SAST10/10 — SAST tool is run on all commits

Evidence and freshness