@jvs-milkdown/crepe
The crêpe editor of [milkdown](https://milkdown.dev/).
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): diff is a well-established package; addition aligns with new inline-diff/diff-block feature exports. | ai | |
| phantom-deps | phantom-dep:@types/lodash-es | AI (phantom-deps): Type-only package; not directly imported at runtime is expected behavior. | ai | |
| phantom-deps | phantom-dep:@codemirror/language | AI (phantom-deps): Used in config/peer context; stable false positive for this editor package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.2.14 | 20 / 5 | |
| 1.2.12 | 19 / 5 | |
| 1.2.11 | 19 / 5 | |
| 1.2.9 | 19 / 0 | |
| 1.2.8 | 19 / 0 | |
| 1.2.3 | 19 / 0 | |
| 1.2.2 | 19 / 0 | |
| 1.1.5 | 17 / 0 |
v1.2.14
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.