← Home

read-yaml

npm Repository Homepage

Very thin wrapper around js-yaml for directly reading in YAML files.

6
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

jonschlinkertshinnn

Keywords

asyncdatafilefsparsereadsyncyamlyml

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): extend-shallow is jonschlinkert's own well-known utility, replacing xtend. No malicious history; consistent with author's ecosystem preferences. ai
provenance publisher-changed AI (provenance): jonschlinkert is the original author of read-yaml; the repo URL points to jonschlinkert/read-yaml. The change from shinnn reflects the original author reclaiming the package, not a hostile takeover. ai

Versions (showing 6 of 6)

Version Deps Published
1.1.0 2 / 3
1.0.0 2 / 2
0.3.1 2 / 2
0.3.0 2 / 3
0.2.0 2 / 4
0.1.0 3 / 4

v1.1.0

2 findings
HIGH Publisher changed: shinnn → jonschlinkert (on 2017-04-02) provenance

This version was published by a different npm account than previous versions on 2017-04-02. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.3.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: jonschlinkert → shinnn (on 2014-12-05) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2014-12-05. This could indicate a legitimate maintainer transition or an account compromise.

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.0

1 finding
LOW No provenance attestation provenance

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

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.