yamljs MIT 18 versions

yamljs

npm Repository Homepage

Standalone JavaScript YAML 1.2 Parser & Encoder. Works under node.js and all major browsers. Also brings command line YAML/JSON conversion tools.

18

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

jeremyfa

Keywords

yamljsonyaml2jsonjson2yaml

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/yaml.debug.js	AI (source-diff): dist/yaml.debug.js is a standard Browserify bundle of the yamljs library — the sample shows readable CoffeeScript-compiled JS with long lines from bundling, not malicious obfuscation.	ai	2026/04/24
source-diff	net-exec-file:test/lib/jasmine-2.0.0/jasmine.js	AI (source-diff): This is the vendored Jasmine 2.0.0 test framework with a clear MIT license header from Pivotal Labs. Network/exec patterns are part of Jasmine's test runner infrastructure, not malware.	ai	2026/04/24

Versions (showing 18 of 18)

Version	Deps	Published
0.3.0	2 / 3	2017-06-24
0.2.10	2 / 3	2017-04-20
0.2.9	2 / 3	2017-04-02
0.2.8	2 / 3	2016-06-22
0.2.7	2 / 3	2016-03-25
0.2.6	2 / 3	2016-02-28
0.2.5	2 / 3	2016-02-16
0.2.4	2 / 0	2015-09-15
0.2.3	5 / 0	2015-05-21
0.2.2	5 / 0	2015-04-29
0.2.1	5 / 0	2014-10-22
0.1.6	2 / 0	2014-09-02
0.1.5	2 / 0	2014-04-23
0.1.4	2 / 0	2012-12-16
0.1.3	2 / 0	2012-09-19
0.1.2	2 / 0	2012-08-13
0.1.1	2 / 0	2012-08-09
0.1.0	0 / 0	2012-08-04

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.