@jvs-milkdown/plugin-highlight
The highlight plugin 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, 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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Consistent across this publisher's 51-version history; no malicious behavior present, just a publish environment change. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Package is part of a monorepo fork with 44 versions; rapid publishes are consistent with bulk/automated monorepo releases. | ai | |
| phantom-deps | phantom-dep:@jvs-milkdown/core | AI (phantom-deps): Same org scope workspace dep; phantom-dep heuristic fires on monorepo workspace references, stable false positive. | ai |
Versions (showing 60 of 60)
| Version | Deps | Published |
|---|---|---|
| 1.2.51 | 4 / 2 | |
| 1.2.50 | 4 / 2 | |
| 1.2.49 | 4 / 2 | |
| 1.2.48 | 4 / 2 | |
| 1.2.47 | 4 / 2 | |
| 1.2.46 | 4 / 2 | |
| 1.2.45 | 4 / 2 | |
| 1.2.44 | 4 / 2 | |
| 1.2.43 | 4 / 2 | |
| 1.2.42 | 4 / 2 | |
| 1.2.41 | 4 / 2 | |
| 1.2.40 | 4 / 2 | |
| 1.2.38 | 4 / 2 | |
| 1.2.37 | 4 / 2 | |
| 1.2.36 | 4 / 2 | |
| 1.2.35 | 4 / 2 | |
| 1.2.34 | 4 / 2 | |
| 1.2.33 | 4 / 2 | |
| 1.2.32 | 4 / 2 | |
| 1.2.31 | 4 / 2 | |
| 1.2.30 | 4 / 2 | |
| 1.2.29 | 4 / 2 | |
| 1.2.28 | 4 / 2 | |
| 1.2.27 | 4 / 2 | |
| 1.2.26 | 4 / 2 | |
| 1.2.25 | 4 / 2 | |
| 1.2.24 | 4 / 2 | |
| 1.2.23 | 4 / 2 | |
| 1.2.22 | 4 / 2 | |
| 1.2.21 | 4 / 2 | |
| 1.2.20 | 4 / 2 | |
| 1.2.18 | 4 / 2 | |
| 1.2.17 | 4 / 2 | |
| 1.2.16 | 4 / 2 | |
| 1.2.15 | 4 / 2 | |
| 1.2.14 | 4 / 2 | |
| 1.2.13 | 4 / 2 | |
| 1.2.12 | 4 / 2 | |
| 1.2.11 | 4 / 2 | |
| 1.2.10 | 4 / 2 | |
| 1.2.9 | 4 / 2 | |
| 1.2.8 | 4 / 2 | |
| 1.2.7 | 4 / 2 | |
| 1.2.5 | 4 / 2 | |
| 1.2.4 | 4 / 2 | |
| 1.2.3 | 4 / 2 | |
| 1.2.2 | 4 / 2 | |
| 1.2.1 | 4 / 2 | |
| 1.2.0 | 4 / 2 | |
| 1.1.9 | 4 / 2 | |
| 1.1.8 | 4 / 2 | |
| 1.1.7 | 4 / 2 | |
| 1.1.6 | 4 / 2 | |
| 1.1.5 | 4 / 2 | |
| 1.1.4 | 4 / 2 | |
| 1.1.3 | 4 / 2 | |
| 1.1.2 | 4 / 2 | |
| 1.1.1 | 4 / 2 | |
| 1.1.0 | 4 / 2 | |
| 1.0.0 | 4 / 2 |
v1.2.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.42
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.41
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.40
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.38
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.37
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.36
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.35
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.34
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.33
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.32
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.31
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.30
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.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] 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.
v1.1.8
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.1.7
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.1.6
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.1.4
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.1.3
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.