@codemirror/lang-yaml
YAML language support for the CodeMirror code editor
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@codemirror/state | AI (phantom-deps): Same-org CodeMirror dependency declared for peer/transitive use; standard pattern across the CodeMirror ecosystem. | ai | |
| phantom-deps | phantom-dep:@codemirror/autocomplete | AI (phantom-deps): Same-org CodeMirror dependency declared for peer/transitive use; standard pattern across the CodeMirror ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Publisher marijn has a strong long-term track record; absence of Sigstore provenance is not a risk signal for this well-established author. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 6.1.3 | 7 / 1 | |
| 6.1.2 | 7 / 1 | |
| 6.1.1 | 6 / 1 | |
| 6.1.0 | 6 / 1 | |
| 6.0.0 | 5 / 1 |
v6.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.