js-yaml
5.5.0 · 15 Oct 2026MIT322.7M / weekRepositoryHomepagenpmAtom feed
Upgrading js-yaml from 2.0.1 to 2.1.3
8 releases in betweenevery note read
- 0
- changes to make
- 1
- advisory fixed
- 2
- new
- 7
- 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.
Fixes 1 advisory affecting 2.0.1
- Deserialization Code Execution in js-yamlcritical · GHSA-xxvw-45rp-3mj2
- 2.0.5
Close security issue in !!js/function constructor. Big thanks to @nealpoole for security audit.
Release by release
- fixed
Fix wrong loading of empty block scalars.
- fixed
- fixed
Fix unwanted line breaks in folded scalars.
- fixed
- fixed
Dumper now respects deprecated booleans syntax from YAML 1.0/1.1
- fixed
Fixed reader bug in JSON-like sequences/mappings.
- fixed
- new
Add standard YAML schemas: Failsafe (
FAILSAFE_SCHEMA), JSON (JSON_SCHEMA) and Core (CORE_SCHEMA). - new
Add
skipInvaliddumper option. - fixed
Bug fix: export
NILconstant from the public interface.
- new
2.0.4 – 2.0.52 releases, nothing new or fixed in the notes
- fixed
Fixed dumping of empty arrays ans objects. ( and {} instead of null)
- fixed
- fixed
Fixed input validation: tabs are printable characters.
- fixed
3 other lines we could not sort, mostly version bumps
- 2.1.0
Rename
DEFAULT_SCHEMAtoDEFAULT_FULL_SCHEMAandSAFE_SCHEMAtoDEFAULT_SAFE_SCHEMA. - 2.1.0
Use
safeLoadforrequireextension. - 2.0.4
Updated .npmignore to reduce package size