@prosekit/basic
A quick starter 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): Transition to GitHub Actions CI publishing with SLSA provenance attestation; consistent with org's CI/CD pipeline adoption. | ai | |
| phantom-deps | phantom-dep:@prosekit/pm | AI (phantom-deps): Same-org sibling dep; declared as runtime dependency, phantom-dep heuristic is a false positive here. | ai |
Versions (showing 94 of 94)
| Version | Deps | Published |
|---|---|---|
| 0.9.5 | 3 / 10 | |
| 0.9.4 | 3 / 10 | |
| 0.9.3 | 3 / 10 | |
| 0.9.2 | 3 / 10 | |
| 0.9.1 | 3 / 10 | |
| 0.9.0 | 3 / 10 | |
| 0.8.0 | 3 / 10 | |
| 0.7.3 | 3 / 9 | |
| 0.7.2 | 3 / 8 | |
| 0.7.1 | 3 / 8 | |
| 0.7.0 | 3 / 8 | |
| 0.6.6 | 3 / 8 | |
| 0.6.5 | 3 / 8 | |
| 0.6.4 | 3 / 8 | |
| 0.6.3 | 3 / 8 | |
| 0.6.2 | 3 / 8 | |
| 0.6.1 | 3 / 8 | |
| 0.6.0 | 3 / 8 | |
| 0.5.4 | 3 / 8 | |
| 0.5.3 | 3 / 5 | |
| 0.5.2 | 3 / 5 | |
| 0.5.1 | 3 / 5 | |
| 0.5.0 | 3 / 5 | |
| 0.4.1 | 3 / 6 | |
| 0.4.0 | 3 / 6 | |
| 0.3.37 | 3 / 6 | |
| 0.3.36 | 3 / 6 | |
| 0.3.35 | 3 / 6 | |
| 0.3.34 | 3 / 6 | |
| 0.3.33 | 3 / 6 | |
| 0.3.32 | 3 / 6 | |
| 0.3.31 | 3 / 6 | |
| 0.3.30 | 3 / 6 | |
| 0.3.29 | 3 / 6 | |
| 0.3.28 | 3 / 6 | |
| 0.3.27 | 3 / 6 | |
| 0.3.26 | 3 / 6 | |
| 0.3.25 | 3 / 6 | |
| 0.3.24 | 3 / 6 | |
| 0.3.23 | 3 / 6 | |
| 0.3.22 | 3 / 6 | |
| 0.3.21 | 3 / 6 | |
| 0.3.20 | 3 / 6 | |
| 0.3.19 | 3 / 6 | |
| 0.3.18 | 3 / 6 | |
| 0.3.17 | 3 / 6 | |
| 0.3.16 | 3 / 6 | |
| 0.3.15 | 3 / 6 | |
| 0.3.14 | 3 / 6 | |
| 0.3.13 | 3 / 6 | |
| 0.3.12 | 3 / 6 | |
| 0.3.11 | 3 / 6 | |
| 0.3.10 | 3 / 6 | |
| 0.3.9 | 3 / 6 | |
| 0.3.8 | 3 / 6 | |
| 0.3.7 | 3 / 6 | |
| 0.3.6 | 3 / 6 | |
| 0.3.5 | 3 / 6 | |
| 0.3.4 | 3 / 6 | |
| 0.3.3 | 3 / 6 | |
| 0.3.2 | 3 / 6 | |
| 0.3.1 | 3 / 6 | |
| 0.3.0 | 3 / 6 | |
| 0.2.5 | 3 / 6 | |
| 0.2.4 | 3 / 6 | |
| 0.2.3 | 3 / 6 | |
| 0.2.2 | 3 / 6 | |
| 0.2.1 | 3 / 6 | |
| 0.2.0 | 3 / 5 | |
| 0.1.0 | 2 / 6 | |
| 0.0.24 | 2 / 6 | |
| 0.0.23 | 2 / 6 | |
| 0.0.22 | 2 / 6 | |
| 0.0.21 | 2 / 6 | |
| 0.0.20 | 2 / 6 | |
| 0.0.19 | 2 / 6 | |
| 0.0.18 | 2 / 6 | |
| 0.0.17 | 2 / 6 | |
| 0.0.16 | 2 / 6 | |
| 0.0.15 | 2 / 6 | |
| 0.0.14 | 2 / 6 | |
| 0.0.13 | 2 / 6 | |
| 0.0.12 | 2 / 6 | |
| 0.0.11 | 2 / 6 | |
| 0.0.10 | 2 / 6 | |
| 0.0.9 | 2 / 6 | |
| 0.0.8 | 2 / 6 | |
| 0.0.7 | 2 / 6 | |
| 0.0.6 | 2 / 6 | |
| 0.0.5 | 2 / 6 | |
| 0.0.4 | 2 / 6 | |
| 0.0.3 | 2 / 4 | |
| 0.0.2 | 2 / 4 | |
| 0.0.1 | 2 / 4 |
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
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.
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.