@prosekit/pm
A re-export of ProseMirror packages
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 the expected pattern for automated releases. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @prosekit/pm; 'pm' stands for ProseMirror, not a typo of 'pg'. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @prosekit/pm; legitimate prosekit monorepo package, not a typo of 'qs'. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.1.18 | 8 / 5 | |
| 0.1.17 | 8 / 5 | |
| 0.1.16 | 8 / 5 | |
| 0.1.15 | 8 / 4 | |
| 0.1.14 | 8 / 4 | |
| 0.1.13 | 8 / 4 | |
| 0.1.12 | 8 / 4 | |
| 0.1.11 | 8 / 5 | |
| 0.1.10 | 8 / 5 |
v0.1.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.16
2 findingsPackage name '@prosekit/pm' is 1 edit(s) away from popular package 'pg'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.12
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.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.