@prosekit/lit
Lit components and utilities 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 is confirmed by SLSA provenance attestation; stable pattern for this package going forward. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped prosekit monorepo package; Levenshtein match to 'vite' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped prosekit monorepo package; Levenshtein match to 'got' is coincidental. | ai |
Versions (showing 89 of 89)
| Version | Deps | Published |
|---|---|---|
| 0.6.7 | 1 / 5 | |
| 0.6.6 | 1 / 5 | |
| 0.6.5 | 1 / 5 | |
| 0.6.4 | 1 / 5 | |
| 0.6.3 | 1 / 5 | |
| 0.6.2 | 1 / 5 | |
| 0.6.1 | 1 / 5 | |
| 0.6.0 | 1 / 5 | |
| 0.5.9 | 1 / 5 | |
| 0.5.8 | 1 / 5 | |
| 0.5.7 | 1 / 4 | |
| 0.5.6 | 1 / 4 | |
| 0.5.5 | 1 / 4 | |
| 0.5.4 | 1 / 4 | |
| 0.5.3 | 1 / 4 | |
| 0.5.2 | 1 / 4 | |
| 0.5.1 | 1 / 4 | |
| 0.5.0 | 1 / 5 | |
| 0.4.16 | 1 / 5 | |
| 0.4.15 | 1 / 5 | |
| 0.4.14 | 1 / 5 | |
| 0.4.13 | 1 / 5 | |
| 0.4.12 | 1 / 5 | |
| 0.4.11 | 1 / 4 | |
| 0.4.10 | 1 / 4 | |
| 0.4.9 | 1 / 4 | |
| 0.4.8 | 1 / 4 | |
| 0.4.7 | 1 / 4 | |
| 0.4.6 | 1 / 4 | |
| 0.4.5 | 1 / 4 | |
| 0.4.4 | 1 / 4 | |
| 0.4.3 | 1 / 4 | |
| 0.4.2 | 1 / 4 | |
| 0.4.1 | 1 / 4 | |
| 0.4.0 | 1 / 4 | |
| 0.3.27 | 1 / 4 | |
| 0.3.26 | 1 / 4 | |
| 0.3.25 | 1 / 4 | |
| 0.3.24 | 1 / 4 | |
| 0.3.23 | 1 / 4 | |
| 0.3.22 | 1 / 4 | |
| 0.3.21 | 1 / 4 | |
| 0.3.20 | 1 / 4 | |
| 0.3.19 | 1 / 4 | |
| 0.3.18 | 1 / 4 | |
| 0.3.17 | 1 / 4 | |
| 0.3.16 | 1 / 4 | |
| 0.3.15 | 1 / 4 | |
| 0.3.14 | 1 / 4 | |
| 0.3.13 | 1 / 4 | |
| 0.3.12 | 1 / 4 | |
| 0.3.11 | 1 / 4 | |
| 0.3.10 | 1 / 4 | |
| 0.3.9 | 1 / 4 | |
| 0.3.8 | 1 / 4 | |
| 0.3.7 | 1 / 4 | |
| 0.3.6 | 1 / 4 | |
| 0.3.5 | 1 / 4 | |
| 0.3.4 | 1 / 4 | |
| 0.3.3 | 1 / 4 | |
| 0.3.2 | 1 / 4 | |
| 0.3.1 | 1 / 4 | |
| 0.2.7 | 10 / 4 | |
| 0.2.6 | 10 / 5 | |
| 0.2.5 | 10 / 5 | |
| 0.2.4 | 10 / 5 | |
| 0.2.3 | 10 / 5 | |
| 0.2.2 | 10 / 5 | |
| 0.2.1 | 10 / 5 | |
| 0.2.0 | 10 / 5 | |
| 0.1.9 | 8 / 5 | |
| 0.1.8 | 7 / 5 | |
| 0.1.7 | 7 / 5 | |
| 0.1.6 | 7 / 5 | |
| 0.1.5 | 7 / 6 | |
| 0.1.4 | 7 / 6 | |
| 0.1.3 | 7 / 6 | |
| 0.1.2 | 7 / 6 | |
| 0.1.1 | 7 / 6 | |
| 0.1.0 | 7 / 6 | |
| 0.0.24 | 7 / 6 | |
| 0.0.23 | 7 / 6 | |
| 0.0.22 | 7 / 6 | |
| 0.0.21 | 7 / 6 | |
| 0.0.20 | 7 / 6 | |
| 0.0.19 | 7 / 6 | |
| 0.0.18 | 7 / 6 | |
| 0.0.17 | 7 / 6 | |
| 0.0.16 | 7 / 6 |
v0.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
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.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
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.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.