Skip to content
| Marketplace
Sign in
Visual Studio Code>Visualization>PatchWRK: API Compatibility ScannerNew to Visual Studio Code? Get it now.
PatchWRK: API Compatibility Scanner

PatchWRK: API Compatibility Scanner

PatchWRK

|
1 install
| (0) | Free
Scan third-party API integrations, identify known compatibility risks, and review evidence-backed findings directly in VS Code.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

PatchWRK: API Compatibility Scanner — Free

Free API Compatibility Scanner for supported third-party API integrations and evidence-backed compatibility reports. The Scanner engine is open source under MIT.

Inspect supported integration evidence, review historical compatibility findings and keep manual scan results locally. No PatchWRK account, API credentials, separate Scanner installation or source compilation needed.

Available publicly in the Visual Studio Marketplace as PatchWRK: API Compatibility Scanner, published by PatchWRK (extension ID PatchWRK.patchwrk-scanner-local) on the normal release channel. Desktop packages target Linux x64 (linux-x64), macOS Intel (darwin-x64) and macOS Apple Silicon (darwin-arm64). See the version and validation scope below.

What you can do

  • Start a genuine manual scan with Run Scan in the PatchWRK sidebar.
  • Discover supported Stripe, OpenAI, Anthropic, Shopify and Twilio SDK evidence.
  • Review evidence-backed assessments from a small offline catalog: four historical Stripe/OpenAI records, not comprehensive or continuously updated API coverage.
  • Open Visual HTML Reports with source references, uncertainty and expandable evidence.
  • Explicitly enable Local Scan History, then save and reopen privacy-filtered snapshots.
  • Compare Scans to review recorded differences without rescanning or editing snapshots.

There is no overall health score. Unknown or absent findings do not establish compatibility; an affected finding is not production runtime verification.

Install and run

The manifest minimum is VS Code 1.137.0; its extension host must use embedded Node.js major 24. A separately installed system Node does not replace that runtime.

Desktop target Extension version Verified scope
Linux x64 (linux-x64) 0.2.6 Native automated installed-editor checks on Ubuntu 24.04.5 LTS, VS Code 1.143.1, host Node 24.21.0
macOS Intel (darwin-x64) 0.2.6 Native automated installed-editor checks on macOS 15.7.9, VS Code 1.143.1, host Node 24.21.0
macOS Apple Silicon (darwin-arm64) 0.2.5 Existing verified release; prior founder/editor acceptance on VS Code 1.137.0 with Node 24

Native automated checks cover scanning, reports, local history, full restart and comparison. Human graphical/native-picker acceptance for Linux x64 and macOS Intel is not claimed. Other distributions, OS/editor versions and Cursor have not been verified. Remote, virtual and web workspaces are unsupported.

  1. Open Install for VS Code and choose Install, or find the exact extension ID in VS Code Extensions. Confirm publisher PatchWRK. No clone, npm/pnpm installation or build step. For a separately supplied, reviewed VSIX, use Extensions → … → Install from VSIX.
  2. Open a stable, authorized local JavaScript/TypeScript project. Trust only a project you are authorized to inspect. Click the official PatchWRK P in the Activity Bar.
  3. Click Run Scan. Choose Reports Only for the simplest first scan, or explicitly enable local history. Find an unanswered choice in VS Code's notification bell.
  4. Review the real report and its limitations. Latest Report reopens it without rescanning.

Scans run only when explicitly requested. No source/configuration code is executed, target dependencies installed, source uploaded, provider requests made, or telemetry collected by PatchWRK. Editor/Marketplace services have their own network behavior.

History and comparison

Enabling history requires selecting an existing parent outside all open projects and confirming the exact new private directory. Only then is a project UUID created. Both directory and project UUID are supplied to the existing Scanner. A reports-only scan is not saved retroactively. No implicit home storage or Cloud synchronization.

Run two explicitly saved scans, then open Scan History or a recent record to reopen saved evidence. Compare Scans asks for two records, orders them by validated original UTC timestamps, and passes older → newer to Scanner. Equal timestamps use ascending UUID order, disclosed in title/status; invalid metadata refuses comparison. Time order does not prove source lineage, an improvement or a repair. Records are immutable.

Choose Configure Local History for guided setup. It explains optional local snapshots and opens VS Code’s native folder picker. Select an existing parent folder, or create one in the picker where your operating system supports it. The final confirmation shows both the chosen parent and the dedicated new history subfolder where future successful scans will be saved. Choose Create History only after reviewing that exact path; Cancel leaves the association unchanged. You never create snapshot files manually. No Cloud account or source upload.

Configure Local History also lets you Disable History without deleting saved snapshots or forgetting the approved location. Reports Only scans then save no new snapshots; existing History and Compare remain available. To resume saving, choose Enable History and confirm the retained directory. It must still be accessible, private and associated with the original project; missing storage is not recreated. Native picker new-folder controls vary by platform; no custom folder-creation UI or automatic scan is added. Interrupted initialization can leave a directory; inspect it rather than automatically retrying or moving storage.

Delete Snapshot previews the selected record and requires explicit modal confirmation. No automatic deletion, retention scheduler or secure-erasure claim.

Privacy and safety

Target scanning is offline and read-only. HTML omits absolute target/output paths, raw arguments and source snippets. Filenames, identifiers, timestamps and approved metadata can still be sensitive: review reports and snapshots privately before sharing. See Privacy and safety, Support and the Scanner security policy.

Reports open in script-disabled panels with restrictive CSP and an extension-only contrast correction for readable dark text on branded light surfaces. Saved HTML and findings stay unchanged. The sidebar uses only a small local, nonce-authorized script with restricted messages; no external fonts/assets or network bridge.

Cancel operation safely abandons pending choices or terminates the active worker. An old editor notification may remain visible: dismiss it; late answers cannot start work. Cancellation may leave a completed/incomplete report, snapshot or lock. Inspect storage before manually retrying. No automatic retry, overwrite or lock cleanup.

Portable filesystem checks require stable checkouts and do not sandbox hostile concurrent mutation. Parser budgets are not hard CPU isolation. Local snapshots are validated, not authenticated. Full independent screen-reader and runtime network observation are not certified. Support is best effort with no SLA.

Scanner and Pro boundaries

These are free local Scanner capabilities. PatchWRK Pro is an upcoming paid API maintenance platform and is not yet available. Its intended workflow is Monitor → Detect → Analyze → Repair → Test → Approve; none of those planned maintenance services is activated by this extension. This extension does not add automatic API monitoring, proactive alerts, advanced Impact Intelligence, AI repairs, automatic migrations, automated verification, developer-approved repair pull requests, hosted history, authentication or billing.

Bundled Scanner source · Scanner CLI — GitHub Releases · Issues · Questions

The public repository contains the Scanner engine. A public source location for the VS Code extension adapter has not been verified; do not infer complete extension source availability from the engine link or MIT licensing.

Support

Report sanitized bugs through GitHub Issues, ask questions in Discussions, and report vulnerabilities through the private security process or security@patchwrk.dev. Never post credentials, private source or raw sensitive reports. Best effort, no SLA.

MIT © 2026 Jovan Simon. See the MIT license, included third-party notices and bundled library licenses. The bundled Scanner includes the reviewed reporting refinements described in the included CHANGELOG.md; the separately published CLI v0.1.0 archive remains a distinct distribution. Extension and CLI version numbers are independent.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft