@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 28 of 28)
| 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 |
v0.17.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
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.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.7
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.
v0.11.6
2 findingsThis version was published by a different npm account than previous versions on 2025-09-29. 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.11.5
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.11.4
2 findingsThis version was published by a different npm account than previous versions on 2025-08-17. 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.11.3
2 findingsThis version was published by a different npm account than previous versions on 2025-08-14. 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.11.2
2 findingsThis version was published by a different npm account than previous versions on 2025-08-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.11.1
2 findingsThis version was published by a different npm account than previous versions on 2025-08-03. 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.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.