← Home

@jvs-milkdown/plugin-cursor

24
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jvs-milkdown

Keywords

milkdownmilkdown plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern rapid-publish AI (publish-pattern): Automated publishing pipeline for a large scoped package family; rapid publish is expected across 43+ versions. ai
provenance no-provenance AI (provenance): New package family; lack of provenance is common and not a risk signal here. ai

Versions (showing 24 of 24)

Version Deps Published
1.2.34 4 / 0
1.2.25 4 / 0
1.2.20 4 / 0
1.2.17 4 / 0
1.2.16 4 / 0
1.2.15 4 / 0
1.2.14 4 / 0
1.2.13 4 / 0
1.2.12 4 / 0
1.2.11 4 / 0
1.2.10 4 / 0
1.2.9 4 / 0
1.2.8 4 / 0
1.2.7 4 / 0
1.2.5 4 / 0
1.2.4 4 / 0
1.2.3 4 / 0
1.2.2 4 / 0
1.2.1 4 / 0
1.1.5 4 / 0
1.1.2 4 / 0
1.1.1 4 / 0
1.1.0 4 / 0
1.0.0 4 / 0

v1.2.34

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jvs-milkdown.

INFO No provenance attestation provenance

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