@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 7 of 107)
| Version | Deps | Published |
|---|---|---|
| 0.0.7 | 2 / 5 | |
| 0.0.6 | 2 / 5 | |
| 0.0.5 | 2 / 5 | |
| 0.0.4 | 2 / 5 | |
| 0.0.3 | 2 / 5 | |
| 0.0.2 | 2 / 5 | |
| 0.0.1 | 2 / 5 |
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.