Fixly — VS Code extension

Scan the open project's npm dependencies — direct and transitive — for known vulnerabilities, using the shared @fixly/core scanner (OSV detection + NVD CVE cross-referencing).

Commands

• Fixly: Scan Current Project (fixly.scanCurrentProject) — reads package.json and package-lock.json from the first workspace folder, resolves the full dependency tree, queries OSV (+ NVD), and opens a report.
• Fixly: Show Last Report (fixly.showReport) — re-opens the report panel (also what clicking the status bar item does).
• Fixly: Apply Remediation Plan (fixly.applyRemediationPlan) — writes the scan's fix plan into package.json: direct upgrades (preserving ^/~ style) and transitive overrides. It first opens a side-by-side diff preview of the proposed package.json and asks to confirm — nothing is written until you click Apply. Malicious packages are never auto-edited; it lists the npm uninstall commands to run by hand. No installs are run and node_modules is untouched — finish with npm install. Also triggered by the Apply Fix Plan button in the report.

In-editor feedback

• Inline diagnostics — every vulnerable direct dependency gets a squiggle on its exact line in package.json (critical/high → error, medium → warning, low → info), with the worst CVE, the finding count, and the fix version in the hover; the diagnostic code links to the advisory. Findings also appear in the Problems panel. Transitive findings live in the report panel (they have no line in package.json to point at).
• Status bar — live severity counts after every scan (e.g. Fixly: 2C 5H 3M), red background when critical/high findings exist, Fixly: clean when there are none. The tooltip shows the Grade Forecast — the grade you'd reach by applying the fix plan. Click to open the report.
• Scan on save — saving package.json or package-lock.json triggers an automatic, quiet rescan (1.2s debounce, so npm install touching both files scans once). Toggle with fixly.scanOnSave.
• Scan as you type (opt-in) — with fixly.scanOnType enabled, editing package.json rescans from the unsaved editor buffer (1.5s debounce), no save required; the saved package-lock.json still supplies the tree.

Settings

NVD API key (optional)

NVD's public API is rate-limited (~5 requests / 30s), so a large project only gets a handful of CVEs cross-referenced per scan. A free key raises the limit — and Fixly then fetches concurrently for wider coverage:

1. Request one at https://nvd.nist.gov/developers/request-an-api-key — free, emailed to you in a minute.
2. Put it in fixly.nvdApiKey (Settings → Extensions → Fixly), or export NVD_API_KEY in the environment VS Code launches from.

Prefer VS Code User settings so the key stays out of your repository. It is masked in the Fixly output channel and only ever sent to NVD.

Report

A webview panel shows:

• The Fixly Score (A–F) with the top fixes, and a Grade Forecast line — the grade you'd reach by applying the fix plan (e.g. "Apply the fix plan → B (86), +34 points") — with an Apply Fix Plan button.
• Summary cards: packages (direct + transitive), total vulnerabilities, and per-severity counts (critical / high / medium / low / unknown).
• A findings table: package (with a transitive chip where relevant), installed version, OSV ID + data sources, CVE, severity, CVSS (with NVD's independent score when cross-referenced), summary, and fix version.
• Warnings (missing lock file, unresolved versions, partial OSV/NVD data).
• Actions: Rescan Project, Copy Summary, Export JSON Report.

The panel refreshes in place after on-save rescans. Diagnostic logs are written to the Fixly output channel.

Develop

pnpm --filter fixly-vscode build      # bundle to dist/extension.js (esbuild)
pnpm --filter fixly-vscode typecheck

Then press F5 in VS Code (Extension Development Host) to run it.

Scope (prototype)

No marketplace packaging, no auth, npm only — same scope as the rest of Fixly. Transitive scanning requires a package-lock.json in the workspace.