← Home

@prosemirror-adapter/vue

5
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

mirone

Keywords

prosemirror-adaptervue

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:prosemirror-keymap AI (phantom-deps): prosemirror-keymap is a declared runtime dependency in package.json; phantom-dep heuristic misfires here. ai
typosquat typosquat.levenshtein:vite AI (typosquat): Scoped package @prosemirror-adapter/vue is not a typosquat of vite; Levenshtein match is spurious. ai
typosquat typosquat.levenshtein:yup AI (typosquat): Scoped package @prosemirror-adapter/vue is not a typosquat of yup; Levenshtein match is spurious. ai

Versions (showing 5 of 5)

Version Deps Published
0.5.3 4 / 2
0.5.2 4 / 2
0.4.6 6 / 3
0.4.5 6 / 3
0.4.2 6 / 3

v0.5.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.5.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.4.6

2 findings
HIGH Publisher changed: mirone → GitHub Actions (on 2025-10-11) provenance

This version was published by a different npm account than previous versions on 2025-10-11. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.4.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.