@prosekit/extensions
A collection of common extensions 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): prosekit migrated to GitHub Actions CI publishing with SLSA attestation; ocavue remains the author in package.json. | ai | |
| dependencies | unvetted-dep:@prosekit/core | AI (dependencies): First-party prosekit monorepo dep; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:prosemirror-math | AI (dependencies): Well-known ProseMirror ecosystem package; expected dep for math extension. | ai | |
| dependencies | unvetted-dep:@prosekit/pm | AI (dependencies): First-party prosekit monorepo dep; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:prosemirror-flat-list | AI (dependencies): Well-known ProseMirror ecosystem package; expected dep for list extension. | ai | |
| dependencies | unvetted-dep:prosemirror-enter-rules | AI (dependencies): Well-known ProseMirror ecosystem package; expected dep for enter-rule extension. | ai | |
| dependencies | unvetted-dep:prosemirror-search | AI (dependencies): Well-known ProseMirror ecosystem package; expected dep for search extension. | ai |
Versions (showing 6 of 106)
| Version | Deps | Published |
|---|---|---|
| 0.0.6 | 3 / 4 | |
| 0.0.5 | 3 / 4 | |
| 0.0.4 | 3 / 4 | |
| 0.0.3 | 3 / 4 | |
| 0.0.2 | 3 / 4 | |
| 0.0.1 | 3 / 4 |
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.