← Home

@prosemark/spellcheck-frontend

npm Repository Homepage

CodeMirror 6 extensions for **showing** spellcheck issues in a ProseMark (or other markdown) editor. This package does not ship a dictionary or spell engine; you supply misspelled ranges and optional suggestion data.

6
Versions
MIT
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

jsimonrichard

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Intentional migration to GitHub Actions CI publishing; SLSA provenance attestation confirms legitimate CI/CD pipeline. ai
phantom-deps phantom-dep:@prosemark/core AI (phantom-deps): Same-org runtime dependency declared in package.json; phantom-dep heuristic false positive for this package. ai

Versions (showing 6 of 6)

Version Deps Published
0.0.6 3 / 0
0.0.5 3 / 0
0.0.4 3 / 0
0.0.3 3 / 0
0.0.2 3 / 0
0.0.1 3 / 0

v0.0.6

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.0.5

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.0.4

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.0.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.0.2

2 findings
HIGH Publisher changed: jsimonrichard → GitHub Actions (on 2026-02-28) provenance

This version was published by a different npm account than previous versions on 2026-02-28. 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.0.1

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.