@milkdown/plugin-history
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from human publisher (mirone) to GitHub Actions CI/CD is confirmed by SLSA provenance attestation; expected for monorepo automation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD migration is consistent with the Milkdown project's release cadence; SLSA attestation confirms legitimate publish. | ai | |
| dependencies | unvetted-dep:@milkdown/ctx | AI (dependencies): Sibling monorepo package; co-released at same version, expected pattern. | ai | |
| dependencies | unvetted-dep:@milkdown/core | AI (dependencies): Sibling monorepo package; co-released at same version, expected pattern. | ai | |
| dependencies | unvetted-dep:@milkdown/prose | AI (dependencies): Sibling monorepo package; co-released at same version, expected pattern. | ai | |
| dependencies | unvetted-dep:@milkdown/utils | AI (dependencies): Sibling monorepo package; co-released at same version, expected pattern. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 7.21.3 | 4 / 0 | |
| 7.21.2 | 4 / 0 | |
| 7.21.1 | 4 / 0 | |
| 7.21.0 | 4 / 0 | |
| 7.20.0 | 4 / 0 | |
| 7.19.2 | 4 / 0 | |
| 7.19.1 | 4 / 0 | |
| 7.19.0 | 4 / 0 | |
| 7.18.0 | 4 / 0 | |
| 7.17.3 | 4 / 0 | |
| 7.17.2 | 4 / 0 | |
| 7.17.1 | 4 / 0 | |
| 7.17.0 | 4 / 0 | |
| 7.16.0 | 4 / 0 | |
| 7.15.5 | 5 / 0 | |
| 7.15.4 | 5 / 0 | |
| 7.15.3 | 5 / 0 | |
| 7.15.2 | 5 / 0 | |
| 7.15.1 | 5 / 0 | |
| 7.15.0 | 5 / 0 | |
| 7.14.0 | 5 / 0 | |
| 7.13.2 | 5 / 0 | |
| 7.13.1 | 5 / 0 | |
| 7.13.0 | 5 / 0 | |
| 7.12.1 | 5 / 0 | |
| 7.12.0 | 5 / 0 | |
| 7.11.1 | 5 / 0 | |
| 7.11.0 | 5 / 0 | |
| 7.10.5 | 5 / 0 | |
| 7.10.4 | 5 / 0 | |
| 7.10.3 | 5 / 0 | |
| 7.10.2 | 5 / 0 | |
| 7.10.1 | 5 / 0 | |
| 7.10.0 | 5 / 0 | |
| 7.9.1 | 5 / 0 | |
| 7.9.0 | 5 / 0 | |
| 7.8.0 | 2 / 3 | |
| 7.7.0 | 2 / 3 | |
| 7.6.4 | 2 / 3 | |
| 7.6.3 | 2 / 3 | |
| 7.6.2 | 2 / 3 | |
| 7.6.1 | 2 / 3 | |
| 7.6.0 | 2 / 3 | |
| 7.5.9 | 2 / 3 | |
| 7.5.8 | 2 / 3 | |
| 7.5.0 | 2 / 3 | |
| 7.4.0 | 2 / 3 | |
| 7.3.6 | 2 / 3 | |
| 7.3.5 | 2 / 3 | |
| 7.3.4 | 2 / 3 | |
| 7.3.3 | 2 / 3 |
v7.21.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.