Extension Lockfile: an allow-list check for your editor extensions (free sample)
by PaperChaseWebb
From Extension Lockfile: the quick checks for the 2026-10-29 Claude Code extension incident, pointing to the vendor's notice, five habits for editor extensions, and a read-only script that flags extensions not on your allow list, at an unapproved version, or installed in the last few days.
- Price
- Free
- Difficulty
- Beginner
- Setup
- 5 min
- Format
- .md file
extension-lockfile-allow-list-check-free-sample.md · 7 KB · direct download, no signup
What you end up with
In a few minutes you know whether the 2026-10-29 notice applies to you and which installed extensions you never approved.
What you get
- Quick checks for the 2026-10-29 incident, with the vendor's notice
- Five habits for editor extensions
- ext_mini.py: an allow-list and cooldown check across five editors
Who it is for
Anyone who wants a quick, read-only look at which editor extensions they have and whether they meant to install them.
Works with
Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free.
Time to result: About five minutes to a first result
Sample prompts, free to use
Run python3 ext_mini.py allow.txt 72 and explain each flagged line in one sentence. Do not uninstall or change anything.
The checks, habits and script are in the file.
Free preview of the file
# Extension Lockfile: an allow-list check for your editor extensions (free sample) Version 1.0, 2026-10-30. By PaperChaseWebb. For anyone using VS Code, Cursor, Windsurf or VSCodium with AI extensions who wants to know what is installed and whether it matches what they meant to install. One Markdown file and one Python 3 script, standard library only, read-only. The script was tested with 4 tests on made-up home folders on Linux with Python 3.13. It was not run on a real macOS or Windows machine or against real editor installs. On 2026-10-29 a tampered build of the Claude Code extension, version 2.1.313, was served from the Cursor extension marketplace for about eleven hours. It tried to add an SSH key and leave startup entries behind. If you use either, start with the vendor's notice, below. Then use this sample to write down what you trust, so the next one is quicker to check. ## First: were you affected by 2026-10-29 Read Cursor's notice: https://cursor.com/blog/claude-code-extension-security-notice . It covers Anthropic.claude-code 2.1.313 installed or updated from the Cursor marketplace between about 2:27am and 1:35pm Pacific time on 2026-10-29, and gives a one-line check for macOS and Windows plus remediation scripts. In short: - Look for the key comment svc-telemetry in ~/.ssh/authorized_keys (on Windows, also C:\ProgramData\ssh\administrators_authorized_keys). - Look for a folder named anthropic.claude-code-2.1.313 followed by a platform under ~/.cursor/extension
Test record
- Date
- Oct 30, 2026
- What was run
- tests/test_mini.py on made-up home folders (clean, drifted, incident), a wildcard allow list and bad inputs, and the copy extracted from the sample page. Linux, Python 3.13.
- Result
- 4 passed, 0 failed; exit 2 on a missing allow list, a bad hours value and a missing argument; the extracted copy was identical to the tested script.
- Not run
- Real macOS, Windows or real editor installs.
Copied from this item's dated test notes. What was not run stays in.
Worth knowing
- The sample checks extensions against an allow list. The lock file, auto-update and sideload checks, the persistence baseline and diff, the incident sweep, the runbook and the tests are in the full pack.
- On 2026-10-30 ext_mini.py passed 4 tests on made-up home folders on Linux with Python 3.13, and the copy extracted from the sample page was byte-identical to the tested script. It was not run on real macOS, Windows or real editor installs.
Questions
Does it change anything?
No. It reads each editor's extensions.json and prints a line per extension. It opens no network connection.
What is in the full pack?
A lock file with block lists and per-editor rules, auto-update and sideload checks, a baseline and diff of SSH keys and startup entries, a sweep with the 2026-10-29 indicator file, an incident runbook, a skill file for Claude Code and Codex, and 37 tests. $24.
Details
Version 1.0 · Updated Oct 30, 2026 · Markdown version of this page
License: Personal and commercial use. Download terms
Related
Extension Lockfile: pin your editor extensions and check for persistence after a bad update
Write down the editor extensions you trust at the versions you reviewed, turn off silent updates, and check every machine against that list with a read-only script. Take a baseline of SSH keys, startup entries, crontab and shell files on a quiet day, so when the next bad extension update is announced you can see what changed in one command. Includes an indicator file and runbook for the 2026-10-29 Claude Code extension incident.
Vet Before You Install: the twelve checks (free sample)
The seat sort and the twelve checks to run before any third-party skill, plugin, MCP server, repo or model touches a real machine, plus one prompt and the decision line. Updated to v1.1.
Five rules, a five-check script, four attack drills and a retry check (free sample)
From Shrink the Attack Surface: five rules for closing what your app exposes, a read-only script that finds five common open doors, four attack drills to try by hand on your own agent (pressure, impersonation, injected tool output, a stale or someone else's yes), and retry_mini.py, a read-only check that a failing tool stops at a budget and asks you.
A per-change watch plan template with five rules and a five-check script (free sample)
From Release Watch: five rules for watching a change after it goes live, a plan template, one prompt that has your agent write the plan from the diff, and a read-only script that checks the plan before anything watches it, with a worked example.