prosemirror-gapcursor 1.3.2

ProseMirror plugin for cursors at normally impossible-to-reach positions

prosemirror-gapcursor@1.3.2 was published on 2023-05-17. Its manifest declares 4 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All prosemirror-gapcursor versions · Permanent reference to 1.3.2 · Latest release

Package specifications

Version1.3.2
License declarationMIT
Published2023-05-17T13:40:12.841Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count4
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size39.97 KiB
Published file count13
Package typemodule
ES module entrydist/index.js
Default entrydist/index.cjs
Side effects declaration["./style/gapcursor.css"]
Direct advisories0
Resolved graph dependencies7
Repository stars37
Repository forks26

Install prosemirror-gapcursor 1.3.2

npm install prosemirror-gapcursor@1.3.2
pnpm add prosemirror-gapcursor@1.3.2
yarn add prosemirror-gapcursor@1.3.2

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Binary-Artifacts10/10 — no binaries found in the repo
Code-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
Maintained0/10 — project is archived
SAST0/10 — no SAST tool detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches

Evidence and freshness