@cocoar/vue-markdown-editor
WYSIWYG Markdown editor for Vue 3 based on Milkdown, with Cocoar Design System styling
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@milkdown/ctx | AI (phantom-deps): Declared as runtime dep for consumers to use; not directly imported in library source is expected for a wrapper package. | ai | |
| phantom-deps | phantom-dep:@milkdown/kit | AI (phantom-deps): Same as @milkdown/ctx — re-exported/peer usage pattern for a Milkdown wrapper library. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 2.7.0 | 12 / 5 | |
| 2.6.0 | 12 / 5 | |
| 2.5.2 | 12 / 5 | |
| 2.5.1 | 12 / 5 | |
| 2.5.0 | 12 / 5 | |
| 2.4.0 | 12 / 5 | |
| 2.3.0 | 12 / 5 | |
| 2.2.1 | 12 / 5 | |
| 2.2.0 | 12 / 5 | |
| 2.1.0 | 12 / 5 | |
| 2.0.0 | 12 / 5 | |
| 1.18.0 | 12 / 5 | |
| 1.17.0 | 12 / 5 | |
| 1.16.0 | 12 / 5 | |
| 1.15.0 | 12 / 5 | |
| 1.14.0 | 11 / 3 | |
| 1.13.1 | 11 / 3 | |
| 1.13.0 | 11 / 3 |
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.