yaml 1.8.3

JavaScript parser and stringifier for YAML

yaml@1.8.3 was published on 2020-03-21. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 6.

All yaml versions · Permanent reference to 1.8.3 · Latest release

Package specifications

Version1.8.3
License declarationISC
Published2020-03-21T00:51:23.126Z
Node.js requirement>= 6
Type declarationsNot declared
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size443.02 KiB
Published file count143
Package typecommonjs
ES module entryNot declared
Default entry./index.js
Side effects declarationNot declared
Direct advisories1
Resolved graph dependencies1
Repository stars1697
Repository forks184

Install yaml 1.8.3

npm install yaml@1.8.3
pnpm add yaml@1.8.3
yarn add yaml@1.8.3

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.

Known direct advisories

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review7/10 — Found 3/4 approved changesets -- score normalized to 7
Security-Policy10/10 — security policy file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained10/10 — 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions9/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies2/10 — dependency not pinned by hash detected -- score normalized to 2
License10/10 — license file detected
Fuzzing10/10 — project is fuzzed
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
SAST10/10 — SAST tool is run on all commits

Evidence and freshness