@prosekit/core
Core features for ProseKit
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): Package migrated to GitHub Actions CI publishing with SLSA attestation; this is expected for automated releases. | ai | |
| dependencies | unvetted-dep:just-map-values | AI (dependencies): just-map-values is a well-known utility from the 'just' library family; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @prosekit/core is a legitimate scoped package in the prosekit ecosystem; Levenshtein match to 'cors' is a false positive. | ai | |
| dependencies | unvetted-dep:@prosekit/pm | AI (dependencies): Internal prosekit ecosystem dependency; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:prosemirror-splittable | AI (dependencies): ProseMirror ecosystem utility; consistent dependency across prosekit versions. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.12.3 | 5 / 8 | |
| 0.12.2 | 5 / 8 | |
| 0.12.1 | 5 / 8 | |
| 0.12.0 | 5 / 8 | |
| 0.11.0 | 6 / 8 | |
| 0.10.0 | 6 / 7 | |
| 0.9.0 | 6 / 8 | |
| 0.8.6 | 8 / 7 | |
| 0.8.5 | 8 / 7 | |
| 0.8.4 | 8 / 8 | |
| 0.8.3 | 8 / 6 | |
| 0.8.2 | 8 / 6 | |
| 0.8.1 | 8 / 6 |
v0.12.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.4
2 findingsThis version was published by a different npm account than previous versions on 2025-09-09. 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.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.