@milkdown/kit
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Aggregator package; description is stable across versions. | ai | |
| dependencies | unvetted-dep:@milkdown/plugin-streaming | AI (dependencies): First-party @milkdown scoped package at matching version; part of the same monorepo release. | ai | |
| dependencies | unvetted-dep:@milkdown/plugin-diff | AI (dependencies): First-party @milkdown scoped package at matching version; part of the same monorepo release. | ai | |
| provenance | publisher-changed | AI (provenance): Milkdown migrated to GitHub Actions CI publishing with SLSA attestation; this is a legitimate and improved supply chain practice. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Meta/aggregator package; empty main and sparse README are expected for a re-export bundle. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped package @milkdown/kit; Levenshtein match to 'vite' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped package @milkdown/kit; Levenshtein match to 'koa' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package @milkdown/kit; Levenshtein match to 'got' is a false positive. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 7.21.1 | 21 / 0 | |
| 7.21.0 | 21 / 0 | |
| 7.20.0 | 18 / 0 | |
| 7.19.2 | 18 / 0 | |
| 7.19.1 | 18 / 0 | |
| 7.19.0 | 18 / 0 | |
| 7.18.0 | 18 / 0 | |
| 7.17.3 | 18 / 0 | |
| 7.17.2 | 18 / 0 | |
| 7.17.1 | 18 / 0 | |
| 7.17.0 | 18 / 0 | |
| 7.16.0 | 18 / 0 | |
| 7.15.5 | 19 / 0 | |
| 7.15.4 | 19 / 0 | |
| 7.15.3 | 19 / 0 | |
| 7.15.2 | 19 / 0 | |
| 7.15.1 | 19 / 0 | |
| 7.15.0 | 19 / 0 | |
| 7.14.0 | 19 / 0 | |
| 7.13.2 | 19 / 0 | |
| 7.13.1 | 19 / 0 | |
| 7.13.0 | 19 / 0 | |
| 7.12.1 | 19 / 0 | |
| 7.12.0 | 19 / 0 | |
| 7.11.1 | 19 / 0 | |
| 7.11.0 | 19 / 0 | |
| 7.10.5 | 19 / 0 | |
| 7.10.4 | 19 / 0 | |
| 7.10.3 | 19 / 0 | |
| 7.10.2 | 19 / 0 | |
| 7.10.1 | 19 / 0 | |
| 7.10.0 | 19 / 0 | |
| 7.9.1 | 19 / 0 |
v7.21.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.19.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.19.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.17.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.17.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.17.1
2 findingsThis version was published by a different npm account than previous versions on 2025-10-11. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.