js-yaml
YAML 1.2 parser and serializer
2
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
vitaly
Keywords
yamlparserserializerpyyaml
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Provenance attestation is a best-practice recommendation; absence is not a security blocker for an established package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 29 new files correspond to expanded type system support and esprima integration; tracked in lib/ directory, not hidden bundles. | ai | |
| dependencies | unvetted-dep:esprima | AI (dependencies): esprima is an established, legitimate AST parser; appropriate for js-yaml's JavaScript function type support. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long dormancy is a signal but not disqualifying for an established package; context shows legitimate maintenance activity. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dependency (esprima) is semantically justified for JavaScript function parsing; not a suspicious injection pattern. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is appropriate for a YAML parser supporting JavaScript function serialization; input validated via AST inspection. | ai |