Starter. For “we’re 2 to 10 people building with coding agents. What should we do about security this week, and this month?”Jack Cable’s A Practical Guide to Security in November 2026 is the best checklist of the season. Read it first. This is our version, for a different reader: a team of 2 to 10 people who ship with coding agents. There’s no security team, and an agent can install a package, edit a workflow or touch a key faster than anyone reviews it. Ten steps: five for this week, five for the next 30 days. Each one says what to do, the command if Penthera can help, and where it can’t. Penthera is free, MIT and offline. A clean run means “nothing found in what it checked”, not “safe”.
This week
1. Know what you expose
List your public domains, previews and staging included, and look at them the way a stranger would.scan_url, which only reaches hosts you list. The checks are passive: TLS, headers, cookies, CORS, exposed files, OpenAPI. It sends no injection payloads.
Limit: it doesn’t log in, so it doesn’t test who can see what behind a login. Scan only domains you own.
2. Keep secrets out of git
Once a key is pushed, rotating it is the only fix. Stop it at the commit:~/.aws or a downloads folder are out of reach.
3. Audit what your agents load
Your agents run code too: skills, MCP servers, hooks, permissions, plugins, rule files.agents grades the setup A to F. --pin writes penthera.lock, so a skill or MCP server that changes later shows up on the next run.
Limit: editor extensions themselves aren’t covered yet. A trojanized Claude Code extension sat in Cursor’s marketplace in October (Cursor’s notice). Check extensions by hand and turn off auto-update where you can.
4. Look before you install
Agents add packages fast. Check a package before any of its code runs:minimumReleaseAge, pnpm settings).
Limit: Penthera doesn’t check whether you’ve set a release-age delay.
5. Know what your packages can do
In the next 30 days
6. Put the checks in CI
init offers the hook and a GitHub workflow. The GitHub Action runs on pull requests. Make CI install from the lockfile (npm ci, not npm install).
Limit: Penthera doesn’t yet flag a CI step that installs without the lockfile.
7. Harden your workflows
Pin actions to a commit SHA, not a tag. Never letpull_request_target check out a pull request’s code. Never put a PR title or branch name straight into a run: script. GitHub’s guide covers all three: Security hardening for GitHub Actions.
Penthera: since 2.3.0, npx penthera@2.4.0 --repo . checks all three (gha-unpinned-action, gha-pwn-request, gha-script-injection). It reads .github/workflows/ and runs nothing.
8. Retire long-lived keys
A key that never expires is a key that works for whoever finds it. Where your platform offers short-lived credentials through OIDC, use them. Vercel’s post Death to long-lived static credentials explains it and sets a deadline for its Marketplace vendors. Limit: Penthera finds hardcoded keys in your code. It can’t rotate or replace them.9. Lock down accounts and devices
This step isn’t Penthera’s, and it matters most:- Passkeys or phishing-resistant MFA on GitHub, your cloud, your registry and your email.
- Sessions bound to the device. Device Bound Session Credentials (DBSC, a W3C draft, in Chrome) tie a login cookie to the machine, so a stolen cookie is worth less. Platforms are starting to build on it: Vercel’s post names DBSC among the standards for secure auth.
- A password manager, device management (MDM) and endpoint protection (EDR) on every laptop with production access.
10. Log it, and plan the bad day
Keep logs you can read when something happens: who deployed, which token was used, from where. Write down who rotates which key, and how, before you need it. Penthera: nothing here either. Your platform and cloud have the logs.What this guide doesn’t cover
- Testing your login and access rules: who can see whose data. Penthera doesn’t log in.
- Your cloud’s settings, your network, your phones.
- Code review by a person or a model. Penthera’s rules decide its findings, and an AI review is a different, complementary check.