js-yaml

5.5.0 · 15 Oct 2026MIT322.7M / weekRepository Homepage npm Atom feed

Same major only

4 releases in betweenevery note read

Other targets from 2.0.5Clears its 4 advisories3.15.0 Latest5.5.0

0
changes to make: 0
advisories fixed: 2
new: 5
fixes

Security

4 advisories still affect 2.1.3

js-yaml has prototype pollution in merge (<<)moderate · GHSA-mh29-5h37-fv8m
Denial of Service in js-yamlmoderate · GHSA-2pr6-76vf-7546
Code Injection in js-yamlhigh · GHSA-8j8c-7jfh-h6hx
JS-YAML: Quadratic-complexity DoS in merge key handling via repeated aliasesmoderate · GHSA-h67p-54hq-rp68

Upgrading to 3.15.0 clears them.

Release by release

2.1.3
15 Oct 20131 fix
- fixed
  Fix wrong loading of empty block scalars.
2.1.2
6 Oct 20131 fix
- fixed
  Fix unwanted line breaks in folded scalars.
2.1.1
1 Oct 20132 fixes
- fixed
  Dumper now respects deprecated booleans syntax from YAML 1.0/1.1
- fixed
  Fixed reader bug in JSON-like sequences/mappings.
2.1.0
5 Jun 20132 new · 1 fix
- new
  Add standard YAML schemas: Failsafe (FAILSAFE_SCHEMA), JSON (JSON_SCHEMA) and Core (CORE_SCHEMA).
- new
  Add skipInvalid dumper option.
- fixed
  Bug fix: export NIL constant from the public interface.

2 other lines we could not sort, mostly version bumps

Rename DEFAULT_SCHEMA to DEFAULT_FULL_SCHEMA and SAFE_SCHEMA to DEFAULT_SAFE_SCHEMA.
2.1.0
Use safeLoad for require extension.
2.1.0

Upgrade to 2.1.3

npm install js-yaml@2.1.3

What 2.1.3 needs

Reading 2.1.3's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 2.1.3. Read once, not stored.

After upgrading

Run the type checker, the linter and the tests.
Build, and look for new deprecation warnings.
Update peer dependencies the new version asks for.
4 advisories still affect 2.1.3.