@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 100 of 106)
| Version | Deps | Published |
|---|---|---|
| 0.17.4 | 15 / 21 | |
| 0.17.3 | 15 / 21 | |
| 0.17.2 | 15 / 22 | |
| 0.17.1 | 15 / 22 | |
| 0.17.0 | 15 / 22 | |
| 0.16.0 | 15 / 22 | |
| 0.15.0 | 15 / 22 | |
| 0.14.2 | 14 / 22 | |
| 0.14.1 | 14 / 21 | |
| 0.14.0 | 12 / 20 | |
| 0.13.0 | 12 / 22 | |
| 0.12.2 | 12 / 21 | |
| 0.12.1 | 12 / 21 | |
| 0.12.0 | 12 / 21 | |
| 0.11.7 | 12 / 21 | |
| 0.11.6 | 12 / 21 | |
| 0.11.5 | 11 / 21 | |
| 0.11.4 | 11 / 21 | |
| 0.11.3 | 11 / 21 | |
| 0.11.2 | 11 / 21 | |
| 0.11.1 | 11 / 21 | |
| 0.11.0 | 11 / 21 | |
| 0.10.1 | 11 / 21 | |
| 0.10.0 | 11 / 14 | |
| 0.9.3 | 11 / 14 | |
| 0.9.2 | 11 / 14 | |
| 0.9.1 | 11 / 14 | |
| 0.9.0 | 11 / 14 | |
| 0.8.0 | 10 / 13 | |
| 0.7.24 | 10 / 13 | |
| 0.7.23 | 10 / 12 | |
| 0.7.22 | 10 / 12 | |
| 0.7.21 | 10 / 12 | |
| 0.7.20 | 10 / 12 | |
| 0.7.19 | 10 / 12 | |
| 0.7.18 | 10 / 12 | |
| 0.7.17 | 10 / 12 | |
| 0.7.16 | 10 / 12 | |
| 0.7.15 | 10 / 12 | |
| 0.7.14 | 10 / 12 | |
| 0.7.13 | 10 / 11 | |
| 0.7.12 | 10 / 11 | |
| 0.7.11 | 10 / 9 | |
| 0.7.10 | 10 / 9 | |
| 0.7.9 | 10 / 6 | |
| 0.7.8 | 10 / 6 | |
| 0.7.7 | 10 / 6 | |
| 0.7.6 | 10 / 6 | |
| 0.7.5 | 9 / 6 | |
| 0.7.4 | 9 / 6 | |
| 0.7.3 | 9 / 5 | |
| 0.7.2 | 9 / 5 | |
| 0.7.1 | 9 / 5 | |
| 0.7.0 | 9 / 5 | |
| 0.6.1 | 8 / 4 | |
| 0.6.0 | 8 / 4 | |
| 0.5.3 | 7 / 4 | |
| 0.5.2 | 7 / 4 | |
| 0.5.1 | 7 / 4 | |
| 0.5.0 | 7 / 4 | |
| 0.4.7 | 7 / 4 | |
| 0.4.6 | 7 / 4 | |
| 0.4.5 | 7 / 4 | |
| 0.4.4 | 7 / 4 | |
| 0.4.3 | 7 / 4 | |
| 0.4.2 | 7 / 4 | |
| 0.4.1 | 6 / 4 | |
| 0.4.0 | 6 / 4 | |
| 0.3.2 | 5 / 5 | |
| 0.3.1 | 5 / 5 | |
| 0.3.0 | 5 / 5 | |
| 0.2.5 | 5 / 5 | |
| 0.2.4 | 5 / 5 | |
| 0.2.3 | 5 / 5 | |
| 0.2.2 | 4 / 5 | |
| 0.2.1 | 4 / 5 | |
| 0.2.0 | 4 / 4 | |
| 0.1.6 | 6 / 4 | |
| 0.1.5 | 6 / 4 | |
| 0.1.4 | 5 / 4 | |
| 0.1.3 | 5 / 4 | |
| 0.1.2 | 5 / 4 | |
| 0.1.1 | 5 / 4 | |
| 0.1.0 | 5 / 4 | |
| 0.0.22 | 5 / 4 | |
| 0.0.21 | 5 / 4 | |
| 0.0.20 | 5 / 4 | |
| 0.0.19 | 5 / 4 | |
| 0.0.18 | 5 / 4 | |
| 0.0.17 | 5 / 4 | |
| 0.0.16 | 5 / 4 | |
| 0.0.15 | 5 / 4 | |
| 0.0.14 | 5 / 4 | |
| 0.0.13 | 5 / 4 | |
| 0.0.12 | 5 / 4 | |
| 0.0.11 | 5 / 4 | |
| 0.0.10 | 5 / 4 | |
| 0.0.9 | 5 / 4 | |
| 0.0.8 | 5 / 4 | |
| 0.0.7 | 3 / 4 |
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.