@prosekit/vue
Vue 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 publisher is a CI/CD automation; SLSA attestation confirms integrity. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation confirms legitimate CI/CD publish; dormancy alone is not a risk here. | ai | |
| dependencies | unvetted-dep:@prosemirror-adapter/vue | AI (dependencies): Legitimate ProseMirror adapter library; expected dependency for this package. | ai | |
| dependencies | unvetted-dep:@prosemirror-adapter/core | AI (dependencies): Legitimate ProseMirror adapter library; expected dependency for this package. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped package @prosekit/vue; Levenshtein match to 'vite' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @prosekit/vue; Levenshtein match to 'yup' is a false positive. | ai |
Versions (showing 100 of 107)
| Version | Deps | Published |
|---|---|---|
| 0.7.6 | 5 / 11 | |
| 0.7.5 | 5 / 11 | |
| 0.7.4 | 5 / 11 | |
| 0.7.3 | 5 / 11 | |
| 0.7.2 | 5 / 11 | |
| 0.7.1 | 5 / 11 | |
| 0.7.0 | 5 / 11 | |
| 0.6.8 | 5 / 9 | |
| 0.6.7 | 5 / 9 | |
| 0.6.6 | 5 / 8 | |
| 0.6.5 | 5 / 8 | |
| 0.6.4 | 5 / 8 | |
| 0.6.3 | 5 / 8 | |
| 0.6.2 | 5 / 8 | |
| 0.6.1 | 5 / 8 | |
| 0.6.0 | 5 / 8 | |
| 0.5.1 | 5 / 8 | |
| 0.5.0 | 5 / 8 | |
| 0.4.17 | 5 / 8 | |
| 0.4.16 | 5 / 8 | |
| 0.4.15 | 5 / 8 | |
| 0.4.14 | 5 / 8 | |
| 0.4.13 | 5 / 8 | |
| 0.4.12 | 5 / 7 | |
| 0.4.11 | 5 / 7 | |
| 0.4.10 | 5 / 7 | |
| 0.4.9 | 5 / 6 | |
| 0.4.8 | 5 / 6 | |
| 0.4.7 | 5 / 6 | |
| 0.4.6 | 5 / 6 | |
| 0.4.5 | 4 / 6 | |
| 0.4.4 | 4 / 6 | |
| 0.4.3 | 4 / 6 | |
| 0.4.2 | 4 / 6 | |
| 0.4.1 | 4 / 6 | |
| 0.4.0 | 4 / 6 | |
| 0.3.30 | 4 / 6 | |
| 0.3.29 | 4 / 6 | |
| 0.3.28 | 4 / 6 | |
| 0.3.27 | 4 / 6 | |
| 0.3.26 | 4 / 6 | |
| 0.3.25 | 4 / 6 | |
| 0.3.24 | 4 / 6 | |
| 0.3.23 | 4 / 6 | |
| 0.3.22 | 4 / 6 | |
| 0.3.21 | 4 / 6 | |
| 0.3.20 | 4 / 6 | |
| 0.3.19 | 4 / 6 | |
| 0.3.18 | 4 / 6 | |
| 0.3.17 | 4 / 6 | |
| 0.3.16 | 4 / 6 | |
| 0.3.15 | 4 / 6 | |
| 0.3.14 | 4 / 6 | |
| 0.3.13 | 4 / 6 | |
| 0.3.12 | 4 / 6 | |
| 0.3.11 | 4 / 6 | |
| 0.3.10 | 4 / 6 | |
| 0.3.9 | 4 / 6 | |
| 0.3.8 | 4 / 6 | |
| 0.3.7 | 4 / 5 | |
| 0.3.6 | 4 / 5 | |
| 0.3.5 | 4 / 5 | |
| 0.3.4 | 4 / 5 | |
| 0.3.3 | 4 / 5 | |
| 0.3.2 | 4 / 5 | |
| 0.3.1 | 4 / 5 | |
| 0.3.0 | 5 / 5 | |
| 0.2.7 | 4 / 5 | |
| 0.2.6 | 4 / 5 | |
| 0.2.5 | 4 / 5 | |
| 0.2.4 | 4 / 5 | |
| 0.2.3 | 4 / 5 | |
| 0.2.2 | 4 / 5 | |
| 0.2.1 | 4 / 5 | |
| 0.2.0 | 4 / 5 | |
| 0.1.6 | 4 / 5 | |
| 0.1.5 | 4 / 5 | |
| 0.1.4 | 4 / 5 | |
| 0.1.3 | 4 / 5 | |
| 0.1.2 | 2 / 5 | |
| 0.1.1 | 2 / 5 | |
| 0.1.0 | 2 / 5 | |
| 0.0.25 | 2 / 5 | |
| 0.0.24 | 2 / 5 | |
| 0.0.23 | 2 / 5 | |
| 0.0.22 | 2 / 5 | |
| 0.0.21 | 2 / 5 | |
| 0.0.20 | 2 / 5 | |
| 0.0.19 | 2 / 5 | |
| 0.0.18 | 2 / 5 | |
| 0.0.17 | 2 / 5 | |
| 0.0.16 | 2 / 5 | |
| 0.0.15 | 2 / 5 | |
| 0.0.14 | 2 / 5 | |
| 0.0.13 | 2 / 5 | |
| 0.0.12 | 2 / 5 | |
| 0.0.11 | 2 / 5 | |
| 0.0.10 | 2 / 5 | |
| 0.0.9 | 2 / 5 | |
| 0.0.8 | 2 / 5 |
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.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. 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.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.25
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.