@prosekit/svelte
Svelte 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@prosekit/pm | AI (dependencies): First-party prosekit monorepo dep; expected for this package. | ai | |
| dependencies | unvetted-dep:@prosekit/web | AI (dependencies): First-party prosekit monorepo dep; expected for this package. | ai | |
| dependencies | unvetted-dep:@prosekit/core | AI (dependencies): First-party prosekit monorepo dep; expected for this package. | ai | |
| dependencies | unvetted-dep:@prosemirror-adapter/core | AI (dependencies): Well-known prosemirror-adapter package; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@prosemirror-adapter/svelte | AI (dependencies): Well-known prosemirror-adapter package; stable dependency for this package. | ai |
Versions (showing 97 of 97)
| Version | Deps | Published |
|---|---|---|
| 0.9.6 | 5 / 12 | |
| 0.9.5 | 5 / 12 | |
| 0.9.4 | 5 / 12 | |
| 0.9.3 | 5 / 12 | |
| 0.9.2 | 5 / 12 | |
| 0.9.1 | 5 / 12 | |
| 0.9.0 | 5 / 12 | |
| 0.8.1 | 5 / 7 | |
| 0.8.0 | 5 / 7 | |
| 0.7.0 | 5 / 9 | |
| 0.6.12 | 5 / 9 | |
| 0.6.11 | 5 / 9 | |
| 0.6.10 | 5 / 9 | |
| 0.6.9 | 5 / 9 | |
| 0.6.8 | 5 / 9 | |
| 0.6.7 | 5 / 9 | |
| 0.6.6 | 5 / 9 | |
| 0.6.5 | 5 / 9 | |
| 0.6.4 | 5 / 9 | |
| 0.6.3 | 5 / 9 | |
| 0.6.2 | 5 / 9 | |
| 0.6.1 | 5 / 9 | |
| 0.6.0 | 4 / 9 | |
| 0.5.5 | 4 / 9 | |
| 0.5.4 | 4 / 9 | |
| 0.5.3 | 4 / 9 | |
| 0.5.2 | 4 / 9 | |
| 0.5.1 | 4 / 9 | |
| 0.5.0 | 4 / 9 | |
| 0.4.21 | 4 / 9 | |
| 0.4.20 | 4 / 9 | |
| 0.4.19 | 4 / 9 | |
| 0.4.18 | 4 / 9 | |
| 0.4.17 | 4 / 9 | |
| 0.4.16 | 4 / 9 | |
| 0.4.15 | 4 / 9 | |
| 0.4.14 | 4 / 9 | |
| 0.4.13 | 4 / 9 | |
| 0.4.12 | 4 / 9 | |
| 0.4.11 | 4 / 9 | |
| 0.4.10 | 4 / 9 | |
| 0.4.9 | 4 / 9 | |
| 0.4.8 | 4 / 9 | |
| 0.4.7 | 4 / 9 | |
| 0.4.6 | 4 / 9 | |
| 0.4.5 | 4 / 9 | |
| 0.4.4 | 4 / 9 | |
| 0.4.3 | 4 / 9 | |
| 0.4.2 | 4 / 9 | |
| 0.4.1 | 4 / 9 | |
| 0.4.0 | 4 / 9 | |
| 0.3.10 | 3 / 9 | |
| 0.3.9 | 3 / 9 | |
| 0.3.8 | 3 / 9 | |
| 0.3.7 | 3 / 9 | |
| 0.3.6 | 3 / 9 | |
| 0.3.5 | 3 / 9 | |
| 0.3.4 | 3 / 9 | |
| 0.3.3 | 3 / 9 | |
| 0.3.2 | 3 / 9 | |
| 0.3.1 | 3 / 9 | |
| 0.3.0 | 4 / 9 | |
| 0.2.7 | 3 / 9 | |
| 0.2.6 | 3 / 9 | |
| 0.2.5 | 3 / 9 | |
| 0.2.4 | 3 / 9 | |
| 0.2.3 | 3 / 9 | |
| 0.2.2 | 3 / 9 | |
| 0.2.1 | 2 / 9 | |
| 0.2.0 | 2 / 9 | |
| 0.1.5 | 2 / 9 | |
| 0.1.4 | 2 / 9 | |
| 0.1.3 | 2 / 9 | |
| 0.1.2 | 2 / 9 | |
| 0.1.1 | 2 / 9 | |
| 0.1.0 | 2 / 9 | |
| 0.0.22 | 2 / 9 | |
| 0.0.21 | 2 / 9 | |
| 0.0.20 | 2 / 9 | |
| 0.0.19 | 2 / 9 | |
| 0.0.18 | 2 / 9 | |
| 0.0.17 | 2 / 9 | |
| 0.0.16 | 2 / 9 | |
| 0.0.15 | 2 / 9 | |
| 0.0.14 | 2 / 9 | |
| 0.0.13 | 2 / 9 | |
| 0.0.12 | 2 / 9 | |
| 0.0.11 | 2 / 9 | |
| 0.0.10 | 2 / 9 | |
| 0.0.9 | 2 / 9 | |
| 0.0.8 | 2 / 9 | |
| 0.0.7 | 2 / 6 | |
| 0.0.6 | 2 / 6 | |
| 0.0.5 | 2 / 6 | |
| 0.0.4 | 2 / 6 | |
| 0.0.3 | 2 / 6 | |
| 0.0.2 | 2 / 6 |
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
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.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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. 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.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.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.
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.