← Home

write-yaml

npm Repository Homepage

Write YAML. Converts JSON to YAML writes it to the specified file.

7
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

dataformatjsonreadwriteyaml

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher transition jonschlinkert→shinnn occurred in June 2015, nearly 10 years ago. shinnn is a well-established publisher with strong track record. This is a stable historical fact, not an active risk. ai
maintainer-change maintainer-added AI (maintainer-change): Maintainer addition of shinnn dates to 2015. shinnn has 538 approved packages and long npm history. This historical change poses no ongoing risk. ai

Versions (showing 7 of 7)

Version Deps Published
1.0.0 3 / 4
0.2.2 4 / 3
0.2.1 3 / 3
0.2.0 3 / 3
0.1.2 3 / 4
0.1.1 3 / 5
0.1.0 3 / 5

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

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: shinnn → jonschlinkert (on 2015-11-17) provenance

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

v0.2.1

2 findings
HIGH Publisher changed: jonschlinkert → shinnn (on 2015-06-18) provenance

This version was published by a different npm account than previous versions on 2015-06-18. 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.

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