@serialport/parser-ready 10.2.0

See our api docs https://serialport.io/docs/api-parser-ready

@serialport/parser-ready@10.2.0 was published on 2022-02-03. Its manifest declares 0 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=12.0.0.

All @serialport/parser-ready versions · Permanent reference to 10.2.0 · Latest release

Package specifications

Version10.2.0
License declarationMIT
Published2022-02-03T23:09:52.247Z
Node.js requirement>=12.0.0
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size1.71 KiB
Published file count3
Package typeNot declared
ES module entryNot declared
Default entry./dist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars5993
Repository forks1007

Install @serialport/parser-ready 10.2.0

npm install @serialport/parser-ready@10.2.0
pnpm add @serialport/parser-ready@10.2.0
yarn add @serialport/parser-ready@10.2.0

Runtime dependencies

  • None declared

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.

    Dangerous-Workflow10/10 — no dangerous workflow patterns detected
    Code-Review1/10 — Found 5/30 approved changesets -- score normalized to 1
    Security-Policy9/10 — security policy file detected
    Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
    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-Dependencies7/10 — dependency not pinned by hash detected -- score normalized to 7
    License10/10 — license file detected
    Fuzzing0/10 — project is not fuzzed
    SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

    Evidence and freshness