@cucumber/messages 32.3.1

JSON schema-based messages for Cucumber's inter-process communication

@cucumber/messages@32.3.1 was published on 2026-04-13. Its manifest declares 2 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 @cucumber/messages versions · Permanent reference to 32.3.1 · Latest release

Package specifications

Version32.3.1
License declarationMIT
Published2026-04-13T21:31:44.670Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size300.77 KiB
Published file count95
Package typemodule
ES module entrydist/esm/src/index.js
Default entrydist/cjs/src/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars41
Repository forks24

Install @cucumber/messages 32.3.1

npm install @cucumber/messages@32.3.1
pnpm add @cucumber/messages@32.3.1
yarn add @cucumber/messages@32.3.1

Runtime dependencies

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.

Code-Review0/10 — Found 0/26 approved changesets -- score normalized to 0
Maintained10/10 — 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
Pinned-Dependencies10/10 — all dependencies are pinned
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Packaging10/10 — packaging workflow detected
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
Security-Policy10/10 — security policy file detected
SAST9/10 — SAST tool detected but not run on all commits

Evidence and freshness