js-yaml 3.4.4

YAML 1.2 parser and serializer

js-yaml@3.4.4 was published on 2015-11-21. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All js-yaml versions · Permanent reference to 3.4.4 · Latest release

Package specifications

Version3.4.4
License declarationMIT
Published2015-11-21T20:20:51.107Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count2
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 entryNot declared
Side effects declarationNot declared
Direct advisories7
Resolved graph dependencies3
Repository stars6636
Repository forks863

Install js-yaml 3.4.4

npm install js-yaml@3.4.4
pnpm add js-yaml@3.4.4
yarn add js-yaml@3.4.4

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-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
Maintained10/10 — 30 commit(s) and 28 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Binary-Artifacts10/10 — no binaries found in the repo
SAST0/10 — no SAST tool detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies3/10 — dependency not pinned by hash detected -- score normalized to 3
License10/10 — license file detected
Fuzzing10/10 — project is fuzzed
Branch-Protection0/10 — branch protection not enabled on development/release branches
Security-Policy4/10 — security policy file detected

Evidence and freshness