penthera 1.6.1 → 1.7.0

package/CHANGELOG.md

@@ -4,6 +4,64 @@ All notable changes to Penthera are documented here. Versioning follows [SemVer]
 
 ## [Unreleased]
 
+## [1.7.0] - 2026-10-19
+
+One view and one command. `npx penthera` now sets Penthera up in a project:
+it detects what is there, asks what to check, runs it offline and offers the
+hook, the PR workflow and the dashboard. `penthera ui` is a single view with
+side panels. The README is rewritten, and the methodology and references
+follow APA 7.
+
+### Added
+
+- **`penthera init`, the setup wizard** (also `npx penthera` with no arguments
+  in a terminal). It detects the project offline (git, framework, npm and
+  Python lockfiles, agent config, a dev server on localhost, an existing hook
+  or workflow), asks one checklist question, runs the code, dependency and AI
+  tooling checks (and the running app, only after you confirm it is yours),
+  then shows the grade per area, the three things to fix first and one report
+  folder, `reports/penthera-<date>/`. It then offers, one yes/no each, the
+  pre-commit hook, a `.github/workflows/penthera.yml` pinned to the release
+  commit SHA (shown as a diff first), `reports/` in `.gitignore`, the fix loop
+  and the dashboard. `--yes` takes the safe defaults and never scans a URL,
+  runs the fix loop or opens the dashboard; `--dry-run` prints the plan.
+  Nothing is committed or pushed. See [docs/commands/init.md](docs/commands/init.md).
+
+### Changed
+
+- **`penthera ui` is one view, like the Claude Code desktop app.** A
+  collapsible left sidebar lists projects (grade, open findings, last scan)
+  and recent runs grouped by project, with "+ New scan" on top and settings
+  behind a gear. The centre is one scrolling stream: the selected project's
+  header (grade, severity bar, trend sparkline), what changed since the last
+  scan, "Fix first" and the findings; a running scan or fix loop streams there
+  as a transcript with Apply / Skip / Stop inline on each diff. A prompt-style
+  bar starts scans, dependency checks, AI tooling audits and the fix loop. The
+  collapsible right panel stacks Environment (egress, folder, git branch),
+  Memory, Dependencies, AI tooling, Evidence and Changes cards, and shows a
+  finding's detail when you pick one. `[` and `]` toggle the side panels, which
+  become drawers at narrow widths. Calmer chrome, one primary action at a time;
+  the themes, `--demo` and every security property are unchanged. New
+  `GET /api/env` reads the branch through the agent's hardened git runner.
+- `penthera-scan` keeps the URL-first wizard that `penthera` used to open.
+
+### Docs
+
+- README rewritten in the voice of "Penthera: Cyber Security Agent". The
+  dashboard screenshots now sit directly under the demo GIF; "Get started" leads
+  with one command (`npx penthera`); features are grouped as before you deploy,
+  what you build with, and after you ship; and a new "Research and
+  methodology" section gives the method, the benchmark numbers, and how to cite
+  Penthera. About 12 KB, down from 19 KB.
+- `docs/references.md` is rendered in APA 7th edition style from
+  `docs/references.bib`, sorted by first author within each topic, with an
+  anchor per BibTeX key. Editors for the three Springer proceedings and the NDSS
+  proceedings titles were added from Crossref. A test covers the formatter.
+- `docs/METHODOLOGY.md` uses APA in-text citations, opens with an abstract and
+  a "How to cite" block that mirrors `CITATION.cff`, and now cites every
+  reference. A test fails if a citation does not resolve or a reference is
+  never cited, and the internal audit checks the "How to cite" version.
+
 ## [1.6.1] - 2026-10-19
 
 The GitHub Action gets its Marketplace name. Nothing else changes.

package/README.md

@@ -1,9 +1,13 @@
 <div align="center">
 
-<img src="assets/penthera-social.jpg" alt="Penthera: open-source security for the apps and AI systems you ship" width="840">
+<img src="assets/penthera-social.jpg" alt="Penthera: Cyber Security Agent" width="840">
 
 <br/><br/>
 
+**Penthera: Cyber Security Agent. Open-source security for the apps and AI systems you ship.**
+
+<br/>
+
 [![npm](https://img.shields.io/npm/v/penthera?color=0000ed)](https://www.npmjs.com/package/penthera)
 ![node](https://img.shields.io/badge/node-%E2%89%A522-0000ed)
 ![license](https://img.shields.io/badge/license-MIT-0000ed)
@@ -14,363 +18,216 @@
 
 <img src="assets/demo.gif" alt="Penthera running an interactive security scan in the terminal" width="760">
 
-</div>
-
----
-
-<div align="center">
-
-### Open-source security for the apps and AI systems you ship.
+<br/><br/>
 
-**Check it before you deploy. Vet what you build with. Keep watching after you
-ship. On your own machine, offline, and free.**
+| `penthera ui`, dark | `penthera ui`, light |
+|---|---|
+| ![The dashboard in the dark theme: projects, findings, and a finding's detail](assets/dashboard/ui-dark.jpg) | ![The dashboard in the light theme: all projects and the side cards](assets/dashboard/ui-light.jpg) |
 
 </div>
 
 ---
 
-## Try it in 60 seconds
-
-No install, no account. Each step runs on your machine and sends nothing to us.
-
-```bash
-npx penthera agents --home          # 1. audit your Claude Code, Cursor and MCP setup
-npx penthera deps                   # 2. what can the packages in this project actually do?
-npx penthera http://localhost:3000  # 3. scan the app you are about to ship
-```
-
-Then read [who it is for](#who-it-is-for), or let your coding agent drive it
-with the [Agent Skill](#run-it).
-
 ## The problem
 
 Teams now ship apps and AI agents faster than anyone can secure them. AI writes
-much of the code. AI pulls in the packages, MCP servers, and skills. And on most
-teams nobody does security full time. Attackers have noticed: 2025 and 2026
+much of the code and pulls in the packages, MCP servers, and skills, and on most
+teams nobody works on security full time. Attackers have adapted: 2025 and 2026
 brought self-spreading npm worms that hijacked AI coding tools, malicious MCP
-servers, poisoned agent skills, and leaked AI provider keys running up large bills.
-
-Commercial platforms answer this from the cloud, for a fee, often with an AI
-deciding what is malicious. **Penthera answers it on your machine, for free,
-with rules you can read.** Think of it as the open-source security team for
-teams that don't have one.
-
-## What it does for you
-
-| | The job | What Penthera does | Command |
-|---|---------|--------------------|---------|
-| **Before you deploy** | Test the app | Scan your localhost or preview URL (TLS, headers, CORS, auth, JWT, IDOR, OAuth, OpenAPI, opt-in injection and fuzzing) and your repo (routes, trust boundaries, secrets including AI keys) | [`penthera <url> --repo .`](docs/commands/scan.md) |
-| | Fix and verify | Deterministic fixes on a local branch, re-scanned to prove they worked, remembered so the next run is sharper. Never pushes | [`penthera agent --loop`](docs/commands/fix.md) |
-| | Block it at commit time | Secrets, risky agent config, and dependency changes stopped before they are committed | [`penthera hook install`](docs/commands/hook.md) |
-| **What you build with** | Vet dependencies | What every npm and Python package can actually do (install scripts, shell, network, env, obfuscation), what an upgrade added, lookalike names, licenses | [`penthera deps --base main`](docs/commands/deps.md) |
-| | Guard installs | Shows what a new package brings before any install script runs, and stops it under your policy | [`penthera install <pkg>`](docs/commands/install.md) |
-| | Review pull requests | Comments the dependency capability diff on every PR that touches the lockfile | [GitHub Action](docs/commands/action.md) |
-| | Audit your AI tooling | Skills, MCP servers, hooks, plugins, and rule files: hidden instructions, unpinned servers, over-broad permissions, silent updates | [`penthera agents --home`](docs/commands/agents.md) |
-| **After you ship** | Report and prove | Reports for developers, owners, and auditors; a hashed, signable evidence bundle; NIS2 and CRA readiness and report drafts | [`penthera <url> --audience auditor --evidence out/`](docs/evidence.md) |
-| | See it all | A local dashboard on 127.0.0.1: where each project stands, findings in plain words, history, deps, AI tooling, evidence, and the fix loop with Apply / Skip / Stop per diff | [`penthera ui`](docs/dashboard.md) |
-| | Keep watching | Scheduled checks of your own production for drift: certificates, headers, new endpoints, keys in bundles, new CVEs in your SBOM | *on the [roadmap](ROADMAP.md)* |
-
-What it is not: a human pentester, a 24/7 SOC, or incident response. It does the
-repeatable checks so the people you do have can spend their time on judgement.
+servers, poisoned agent skills, and leaked AI provider keys. Penthera does the
+repeatable security work on your own machine, with rules you can read, so the
+people you have can spend their time on judgement.
 
-## Who it is for
+## Get started
 
-| You are | Start here |
-|---|---|
-| A solo founder or vibecoder about to launch | [Before launch](docs/use-cases/solo-founder.md) |
-| A team adopting Claude Code or Cursor | [The AI-tooling supply chain](docs/use-cases/ai-coding-teams.md) |
-| An open-source maintainer | [For maintainers](docs/use-cases/open-source-maintainers.md) |
-| An EU SME with NIS2 or CRA duties | [Evidence for NIS2 and the CRA](docs/use-cases/eu-sme-compliance.md) |
-| An agency shipping client apps | [A repeatable handover check](docs/use-cases/agencies.md) |
+One command in your project folder, no install, no account:
 
-## Why you can trust it
-
-- **Local and offline.** No account, no telemetry, no cloud. `--offline` limits
-  network traffic to the target you named, and every report lists the hosts that
-  were contacted.
-- **Deterministic, not an AI verdict.** Rules you can read, with `file:line`
-  evidence and a confidence label on every finding. No model decides what is
-  malicious.
-- **Never acts behind your back.** The fix loop works on a local branch, asks
-  before every change by default, and never pushes or opens pull requests.
-- **No update channel to hijack.** Detection rules ship inside reviewed releases.
-  Nothing is downloaded and executed at run time.
-- **Releases you can verify.** Published with npm provenance through trusted
-  publishing, and each version is approved by a maintainer with 2FA before it
-  goes live. SHA-pinned CI, CodeQL, and OpenSSF Scorecard.
-- **Measured and cited.** A published [methodology](docs/METHODOLOGY.md),
-  [48 verified references](docs/references.md), and a reproducible
-  [benchmark](bench/RESULTS.md) with precision and recall.
-
-## By the numbers
-
-Penthera has no customer logos yet. Here is what can be checked instead.
-
-| | |
-|---|---|
-| Benchmark, labelled local targets | precision 0.86, recall 0.90 (19 true positives, 3 false positives, 2 misses; [every one listed](bench/RESULTS.md)) |
-| Detection rules, all readable | 14 URL scan templates, 20 secret and AI-key patterns, 15 dependency capabilities, 39 AI-tooling audit rules, 5 fix recipes |
-| Tests | 687 in the suite, run on Node 22 and 24 on every push |
-| Release gate | an [internal audit](docs/internal-audit.md) of 8 gates (tests, benchmark drift, self-scan, CLI smoke, packaging, offline egress, supply chain, docs links); [latest report](audit/REPORT.md) |
-| Research | a [methodology](docs/METHODOLOGY.md) backed by [48 cited references](docs/references.md) |
-| Supply chain of Penthera itself | [OpenSSF Scorecard](https://scorecard.dev/viewer/?uri=github.com/danoszz/penthera), SHA-pinned CI, CodeQL, npm provenance, each release staged and approved with 2FA |
-| Network calls in `--offline` mode | only the target you named; the benchmark run made 0 requests to non-loopback hosts |
-
-Counts as of 2026-10-19. Refresh them with `npm run docs:numbers` (add
-`-- --tests` to count tests), `npm run bench` and `npm run audit:internal`. The benchmark targets are small and written
-by the same people as the scanner, so they catch regressions rather than
-measure real-world accuracy; see [its limits](bench/RESULTS.md#limits-of-these-numbers).
-
----
-
-## How Penthera fits with other tools
-
-Penthera is meant to sit next to the tools you already use. Its SARIF output
-goes straight into GitHub code scanning, for example. Each comparison page says
-where the other tool goes further and how to run the two together.
-
-| | Focus | Where it runs | How it decides |
-|---|---|---|---|
-| **Penthera** | Your app, your dependencies, your AI tooling, fixes, EU evidence | Your machine or CI, offline | Readable deterministic rules, with evidence |
-| [Socket](docs/compare/socket.md) | Supply-chain risk across package registries | Cloud service, GitHub App, CLI | Registry-scale package analysis, including AI review |
-| [Snyk](docs/compare/snyk.md) | Known vulnerabilities in dependencies, code, containers, IaC | Cloud service, IDE, CLI | Curated vulnerability database plus static analysis |
-| [GitHub Dependabot and code scanning](docs/compare/github.md) | Known-CVE alerts, update PRs, CodeQL | GitHub | Advisory database, CodeQL queries |
-| [OWASP ZAP](docs/compare/zap.md) | Dynamic testing of web apps | Your machine or CI | Active and passive scan rules |
-| [Semgrep](docs/compare/semgrep.md) | Static analysis of your own code | Your machine, CI, cloud platform | Pattern rules, plus a paid cross-file engine |
-
-All comparisons: [docs/compare/](docs/compare/README.md). Corrections are welcome by pull request.
-
----
+```bash
+npx penthera
+```
 
-## Run it
+This is the guided start (`penthera init`). Penthera detects your setup
+offline, asks what to check, and runs the code, dependency, and AI-tooling
+checks. It scans your running app only after you confirm the app is yours. You
+get a grade per area, the three things to fix first, and one report folder.
+Then it offers, one yes or no at a time, the pre-commit hook, a CI workflow, and
+the dashboard. Nothing is committed or pushed. Details are in
+[docs/commands/init.md](docs/commands/init.md).
 
-**As an Agent Skill (recommended).** Let Claude Code, Cursor or [40+ other
-agents](https://agentskills.io/clients) drive it, then ask "scan my app for
-security issues", "is this package safe to add?", or "audit my MCP servers":
+When you know what you want, run it directly:
 
 ```bash
-npx skills add danoszz/penthera
+npx penthera http://localhost:3000 --repo .   # scan the app you are about to ship, and its source
+npx penthera deps                             # what can the packages in this project actually do?
+npx penthera agents --home                    # audit your Claude Code, Cursor and MCP setup
+npx penthera ui                               # open the local dashboard on 127.0.0.1
 ```
 
-**As a CLI.** `npx penthera https://your-app.example`, or install it with the
-one-line installer, which also links the skill into Cursor and Claude Code:
+To let your coding agent drive it, add the Agent Skill, then ask "scan my app
+for security issues" or "is this package safe to add?":
 
 ```bash
-curl -fsSL https://raw.githubusercontent.com/danoszz/penthera/main/install.sh | bash
+npx skills add danoszz/penthera
 ```
 
-Run `penthera` with no arguments for a guided wizard. Other install routes
-(Claude Code plugin, Claude.ai upload, per-project copy) are in
-[docs/commands/skill.md](docs/commands/skill.md).
+The skill tells your agent to refuse targets you do not own or are not
+authorized to test. Other install routes (the one-line installer, the Claude
+Code plugin, a per-project copy) are in [docs/commands/skill.md](docs/commands/skill.md).
+Penthera needs Node.js 22 or later. To run it in a container:
+`docker build -t penthera . && docker run --rm penthera https://your-app.example`.
 
-> The skill adds an authorization gate: it instructs your agent to refuse targets
-> you do not own or are not authorized to test.
 
-### What you get
+## What it does
 
-```
-  Findings
-
-  HIGH  IDOR/BOLA: GET /api/users/{user_id}
-         http://localhost:3000/api/users/1 → 200
-  HIGH  OAuth open redirect
-         http://localhost:3000/api/oauth/callback?redirect_uri=... → 302
-  MED   Missing Content-Security-Policy
-  MED   No login rate limiting detected
-         http://localhost:3000/api/login → 401
-  LOW   Missing X-Frame-Options
-  INFO  Missing Referrer-Policy
-
-  ──────────────────────────────────────────────────────────
-  2 high · 5 medium · 2 low · 2 info
-```
-
-Every finding carries a confidence label (`confirmed`, `likely`, `potential`,
-`needs-human-review`), so a heuristic never poses as a certainty. Reports come
-out as Markdown, JSON, and SARIF, with the fixes in priority order.
+### Before you deploy
 
-## Commands
-
-| Command | What it does | Details |
+| Job | What Penthera does | Command |
 |---|---|---|
-| `penthera <url> [--repo .]` | Black-box and white-box scan; `--profile quick\|standard\|deep` | [scan.md](docs/commands/scan.md) |
-| `penthera agents [--home] [--pin]` | Audit skills, MCP servers, hooks, permissions, plugins, rule files; graded A to F | [agents.md](docs/commands/agents.md) |
-| `penthera deps [--base main]` | Capabilities of every npm and Python package, upgrade diff, typosquats, `--license-policy` | [deps.md](docs/commands/deps.md) |
-| `penthera install <pkg>` | Install firewall: review before any install script runs | [install.md](docs/commands/install.md) |
-| `penthera fix --plan`, `penthera agent --loop` | Deterministic fixes as diffs; the local scan, fix, verify, learn loop | [fix.md](docs/commands/fix.md) |
-| `penthera hook install` | Pre-commit hook on staged changes, about 0.1 to 0.5 s | [hook.md](docs/commands/hook.md) |
-| `uses: danoszz/penthera@<sha>` | PR comment with the capability diff, plus SARIF | [action.md](docs/commands/action.md) |
-| `penthera --machine` | macOS checks (persistence, keyloggers, rootkits) | [scan.md](docs/commands/scan.md) |
-| `penthera ui [--open] [--demo]` | Local dashboard on 127.0.0.1; runs scans and the fix loop from the page | [dashboard.md](docs/dashboard.md) |
-
-Scans, `agents` and `deps` write Markdown, JSON and SARIF (`--markdown`,
-`--json`, `--sarif`). Exit code `1` means critical or high findings, `2` means
-the scan failed.
-
-| `penthera ui`, dark | `penthera ui`, light |
-|---|---|
-| ![The dashboard overview in the dark theme](assets/dashboard/overview-dark.jpg) | ![The dashboard overview in the light theme](assets/dashboard/overview-light.jpg) |
-
-## How it works
-
-```mermaid
-flowchart LR
-    U["You / your AI agent"] --> P((Penthera))
-
-    P --> APP["Your app<br/>black-box URL scan<br/>white-box repo scan"]
-    P --> DEP["Your dependencies<br/>capabilities, upgrade diff<br/>install firewall, typosquats"]
-    P --> AI["Your AI tooling<br/>skills, MCP, hooks<br/>plugins, rule files"]
-
-    APP --> F[["Findings<br/>severity, confidence<br/>evidence, sources"]]
-    DEP --> F
-    AI --> F
-
-    F --> FIX["Fix loop<br/>local branch, re-scan<br/>learn, never push"]
-    FIX -.verified.-> F
-    F --> R["Reports<br/>terminal, Markdown, JSON<br/>SARIF, audience views"]
-    F --> E["Evidence<br/>hashed, signable bundle<br/>NIS2 readiness"]
-```
-
-Findings map to the [OWASP Web Security Testing Guide](docs/owasp-wstg-coverage.md)
-(WSTG v4.2), and agent findings to the OWASP MCP and Agentic Top 10s. The
-default scan is non-destructive. Payload-based testing is opt-in (`--deep`,
-`--fuzz`, `--all`) and gated behind explicit confirmation.
-
----
-## Compliance: NIS2 and the CRA
-
-Shipping in the EU? NIS2 (the Cyberbeveiligingswet in the Netherlands, the
-NIS2-wet in Belgium) puts a duty of care on in-scope organisations, and the
-Cyber Resilience Act adds reporting duties for products with digital elements.
-Penthera turns the technical, testable part into repeatable evidence: an
-Article 21(2) coverage table (`--framework nis2`), a readiness report, policy
-templates, incident and CRA Article 14 report drafts with deadlines, a CycloneDX
-SBOM and AI-BOM, and prefilled customer questionnaires. Offline, no accounts.
-Guides: [NIS2](docs/compliance-nis2.md) and [CRA](docs/compliance-cra.md).
-
-> Readiness tooling, not a certification and not legal advice.
-
----
-
-## Ethical use & authorization
-
-Penthera sends HTTP requests to the targets you give it. Some modes (`--deep`,
-`--fuzz`, `--all`) send attack payloads designed to find vulnerabilities. Use it
-responsibly.
+| Test the app | Scans your localhost or preview URL (TLS, headers, CORS, auth, JWT, IDOR, OAuth, OpenAPI; injection and fuzzing on request) and your repository (routes, trust boundaries, secrets including AI keys) | [`penthera <url> --repo .`](docs/commands/scan.md) |
+| Fix and verify | Applies deterministic fixes on a local branch, re-scans to prove they worked, and remembers the result. Never pushes | [`penthera agent --loop`](docs/commands/fix.md) |
+| Block it at commit time | Stops secrets, risky agent config, and dependency changes before they are committed | [`penthera hook install`](docs/commands/hook.md) |
 
-**You may use Penthera when:**
-
-- You **own** the target (your app, your server, your project).
-- You have **written authorization** from the system owner (email, ticket, signed scope).
-- You scan **localhost** or private lab environments you control.
-- You use it for **defensive security**: research, coursework, CI hardening, pre-release audits.
-
-**You must not use Penthera to:**
-
-- Scan systems you do not own or lack explicit permission to test.
-- Probe government, healthcare, financial, or third-party production systems without authorization.
-- Exfiltrate data, disrupt services, or bypass access controls.
-- Use findings to attack, extort, or harm anyone.
-
-> Before scanning any URL that is not localhost, confirm you have permission.
-> **When in doubt, do not scan.**
-
-Unauthorized security testing may violate computer-misuse laws (for example the US
-CFAA, the UK Computer Misuse Act, and EU national equivalents) and can result in
-criminal prosecution, civil liability, IP blocking, account termination, and
-academic or professional penalties.
-
----
+### What you build with
 
-## Install
+| Job | What Penthera does | Command |
+|---|---|---|
+| Vet dependencies | Shows what every npm and Python package can do (install scripts, shell, network, env, obfuscation), what an upgrade added, lookalike names, and licenses | [`penthera deps --base main`](docs/commands/deps.md) |
+| Guard installs | Shows what a new package brings before any install script runs, and stops it under your policy | [`penthera install <pkg>`](docs/commands/install.md) |
+| Review pull requests | Comments the dependency capability diff on every PR that touches the lockfile | [GitHub Action](docs/commands/action.md) |
+| Audit your AI tooling | Checks skills, MCP servers, hooks, plugins, and rule files for hidden instructions, unpinned servers, over-broad permissions, and silent updates | [`penthera agents --home`](docs/commands/agents.md) |
 
-Requirements: Node.js 22+ and npm. To install from source:
+### After you ship
 
-```bash
-git clone https://github.com/danoszz/penthera.git
-cd penthera && npm install && npm link   # exposes `penthera` globally
-```
+| Job | What Penthera does | Command |
+|---|---|---|
+| Report and prove | Writes reports for developers, owners, and auditors; a hashed, signable evidence bundle; NIS2 and CRA readiness reports and drafts | [`penthera <url> --audience auditor --evidence out/`](docs/evidence.md) |
+| See it all | A local dashboard on 127.0.0.1: one view with your projects, findings in plain words, history, side panels for dependencies, AI tooling and evidence, and the fix loop with Apply, Skip, and Stop per diff | [`penthera ui`](docs/dashboard.md) |
+| Keep watching | Scheduled checks of your production for drift: certificates, headers, new endpoints, keys in bundles, new CVEs in your SBOM | on the [roadmap](ROADMAP.md) |
 
-Or in a container: `docker build -t penthera . && docker run --rm penthera https://your-app.example`.
+Every finding carries a severity, a confidence label (`confirmed`, `likely`,
+`potential`, `needs-human-review`), its evidence, and the research behind it.
+Reports come out as Markdown, JSON, and SARIF for GitHub code scanning. Exit
+code `1` means critical or high findings. Every command and flag is in
+[docs/commands/](docs/commands/README.md).
 
-## Testing and contributing
+Penthera is not a human pentester, a 24/7 SOC, or incident response. It does
+the checks that can be automated reliably and says plainly which ones need a
+person.
 
-```bash
-npm test                 # full suite (live integration tests skip without a running target)
-npm run pentest:mock     # offline tests against a local mock vuln API
-npm run bench            # precision and recall on labelled local targets
-```
+## Why you can trust it
 
-How Penthera decides what is a finding, how sure it is, and what it cannot see
-is in [docs/METHODOLOGY.md](docs/METHODOLOGY.md), with every design choice tied
-to a [reference](docs/references.md). See [CONTRIBUTING.md](CONTRIBUTING.md) for
-the project layout and release checklist, and the [roadmap](ROADMAP.md) for what
-is next. To cite Penthera, use the "Cite this repository" button on GitHub
-([CITATION.cff](CITATION.cff)).
+- **Local and offline.** No account, no telemetry, no cloud. `--offline` limits
+  network traffic to the target you named, and every report lists the hosts it
+  contacted.
+- **Deterministic.** Rules you can read, with `file:line` evidence. No model
+  decides what is malicious.
+- **Non-destructive by default.** The default scan sends only requests a
+  browser would send. Payload testing (`--deep`, `--fuzz`, `--all`) is opt-in
+  and asks for confirmation.
+- **Never acts behind your back.** The fix loop works on a local branch, asks
+  before every change by default, and never pushes or opens pull requests.
+- **No update channel to hijack.** Detection rules ship inside reviewed
+  releases. Nothing is downloaded and executed at run time.
+- **Releases you can verify.** npm provenance through trusted publishing, a
+  maintainer approval with 2FA for every version, SHA-pinned CI, CodeQL, and
+  OpenSSF Scorecard. Every release passes an
+  [internal audit](docs/internal-audit.md) of eight gates
+  ([latest report](audit/REPORT.md)).
+
+## Research and methodology
+
+Penthera's method is written down and tied to the literature. The
+[methodology](docs/METHODOLOGY.md) states the threat model, separates what
+black-box (HTTP) and white-box (source) analysis can and cannot observe, and
+defines a confidence model that keeps heuristics from posing as facts. Each
+probe has explicit false-positive controls, such as randomized canaries and
+repeated timing measurement, and each design choice cites the research or
+standard it rests on: 49 verified references, listed in APA style in
+[docs/references.md](docs/references.md).
+
+| Measure | Result |
+|---|---|
+| Precision on the bundled benchmark | 0.86 (19 true positives, 3 false positives) |
+| Recall on the bundled benchmark | 0.90 (2 misses, [each one explained](bench/RESULTS.md)) |
+| Requests to non-loopback hosts during the benchmark | 0 |
+| Detection rules, all readable | 14 URL scan templates, 20 secret and AI-key patterns, 15 dependency capabilities, 39 AI-tooling rules, 5 fix recipes |
 
-## Status
+The benchmark targets are small and were written by the same people as the
+scanner, so the numbers catch regressions rather than measure real-world
+accuracy ([limits](bench/RESULTS.md#limits-of-these-numbers)). Counts as of
+2026-10-19; refresh them with `npm run docs:numbers` and `npm run bench`.
 
-App scanning (URL, repo, macOS machine), dependency capability analysis and an
-install firewall, the AI-tooling audit, the local fix loop with a learning
-store, audience reports and evidence bundles, the PR-comment GitHub Action, the
-pre-commit hook, and NIS2 and CRA readiness tooling are all shipped. See the
-[CHANGELOG](CHANGELOG.md) for the history. Issues and PRs welcome.
+**Cite this repository.** Use the button on GitHub, or the metadata in
+[CITATION.cff](CITATION.cff). The APA and BibTeX forms are in the
+[methodology](docs/METHODOLOGY.md#how-to-cite).
 
----
+## How it fits with other tools
 
-## Support Penthera
+Penthera works next to the tools you already use. Its SARIF output goes
+straight into GitHub code scanning, for example. Each comparison page says where
+the other tool goes further and how to run the two together.
 
-Penthera is free and MIT-licensed. If it caught something before you shipped it,
-you can help keep it maintained:
+| | Focus | Where it runs | How it decides |
+|---|---|---|---|
+| **Penthera** | Your app, dependencies, and AI tooling; fixes; EU evidence | Your machine or CI, offline | Readable deterministic rules, with evidence |
+| [Socket](docs/compare/socket.md) | Supply-chain risk across package registries | Cloud service, GitHub App, CLI | Registry-scale package analysis, including AI review |
+| [Snyk](docs/compare/snyk.md) | Known vulnerabilities in dependencies, code, containers, IaC | Cloud service, IDE, CLI | Curated vulnerability database plus static analysis |
+| [GitHub Dependabot and code scanning](docs/compare/github.md) | Known-CVE alerts, update PRs, CodeQL | GitHub | Advisory database, CodeQL queries |
+| [OWASP ZAP](docs/compare/zap.md) | Dynamic testing of web apps | Your machine or CI | Active and passive scan rules |
+| [Semgrep](docs/compare/semgrep.md) | Static analysis of your own code | Your machine, CI, cloud platform | Pattern rules, plus a paid cross-file engine |
 
-[![Sponsor on GitHub](https://img.shields.io/badge/Sponsor-GitHub-db61a2?logo=githubsponsors)](https://github.com/sponsors/danoszz)
+All comparisons: [docs/compare/](docs/compare/README.md). Corrections are
+welcome by pull request.
 
-| Tier | Monthly | You get |
-|------|---------|---------|
-| Individual | $5 | Thanks, and your name on the GitHub sponsors list |
-| Supporter | $25 | A mention in the next release notes |
-| Startup | $100 | Your name and link in this README |
-| Company | $500 | Your logo in this README, and a quarterly roadmap call |
+## Use cases
 
-Sponsorship pays for maintainer time: keeping detection rules current, security
-fixes, and the [roadmap](ROADMAP.md). It does not buy influence over findings,
-a support SLA, or early access to vulnerability reports, and a logo here is not
-a security endorsement of that company. Details in
-[docs/funding/sponsor-tiers.md](docs/funding/sponsor-tiers.md).
+| You are | Start here |
+|---|---|
+| A solo founder or vibecoder about to launch | [Before launch](docs/use-cases/solo-founder.md) |
+| A team adopting Claude Code or Cursor | [The AI-tooling supply chain](docs/use-cases/ai-coding-teams.md) |
+| An open-source maintainer | [For maintainers](docs/use-cases/open-source-maintainers.md) |
+| An EU SME with NIS2 or CRA duties | [Evidence for NIS2 and the CRA](docs/use-cases/eu-sme-compliance.md) ([NIS2 guide](docs/compliance-nis2.md), [CRA guide](docs/compliance-cra.md)) |
+| An agency shipping client apps | [A repeatable handover check](docs/use-cases/agencies.md) |
 
----
+Compliance output is readiness tooling. It is not a certification and not
+legal advice.
 
 ## Privacy
 
 Penthera has no telemetry and does not phone home. Scan traffic goes to the
 target you name, reports stay on your machine, and every scan lists any
-third-party host it contacted. With `--offline` the HTTP client refuses every
+third-party host it contacted. With `--offline`, the HTTP client refuses every
 host except the target. Which hosts a normal scan may contact, and why, is in
 [docs/privacy.md](docs/privacy.md).
 
----
+## Ethics and authorization
 
-## Disclaimer
+Penthera sends HTTP requests to the targets you give it, and some modes
+(`--deep`, `--fuzz`, `--all`) send attack payloads. Scan only what you own, what
+you have written authorization to test, or local environments you control.
+Do not use it to probe third-party systems, exfiltrate data, disrupt services,
+or harm anyone. Unauthorized testing may break computer-misuse laws such as the
+US CFAA, the UK Computer Misuse Act, and their EU equivalents. When in doubt, do
+not scan.
 
-Penthera is provided for legitimate security research and defensive testing of
-systems you own or are authorized to test, and for that purpose only.
+The software is provided "as is", without warranty, for defensive testing of
+systems you own or are authorized to test. The author accepts no liability for
+misuse, and you are responsible for making sure every scan you run is lawful.
 
-- It is a research and self-assessment tool. Scan your own apps to find and fix
-  weaknesses before attackers do.
-- The same capabilities that harden a system can cause harm if pointed at someone
-  else's. Use it carefully and lawfully.
-- The author does not condone unauthorized or malicious use, and accepts no
-  liability for any damage, loss, or legal consequence arising from use or misuse
-  of this software.
-- The software is provided "as is", without warranty of any kind. See [LICENSE](LICENSE) (MIT).
-- You are solely responsible for ensuring every scan you run is authorized and
-  legal in your jurisdiction.
+## Contributing and support
 
-By using Penthera you accept these terms.
+Clone the repository and run `npm install`, then `npm test` for the suite and
+`npm run bench` for precision and recall.
+[CONTRIBUTING.md](CONTRIBUTING.md) covers the project layout and the release
+checklist, and the [roadmap](ROADMAP.md) shows what is next. Issues and pull
+requests are welcome.
 
----
+Penthera is free. If it caught something before you shipped it, you can
+[sponsor its maintenance](https://github.com/sponsors/danoszz). Sponsorship pays
+for maintainer time and buys no influence over findings
+([tiers](docs/funding/sponsor-tiers.md)).
 
-## License & disclosure
+## License
 
-MIT. See [LICENSE](LICENSE). Report vulnerabilities in Penthera itself via
-[SECURITY.md](SECURITY.md). Only scan systems you own or are authorized to test.
+MIT. See [LICENSE](LICENSE). Report vulnerabilities in Penthera itself through
+[SECURITY.md](SECURITY.md).

package/bin/scan.js

@@ -4,7 +4,7 @@
  * Alias: penthera-scan
  */
 import { readFileSync } from "node:fs";
-import { runOnboarding } from "../src/cli/onboarding.js";
+import { runScanWizard } from "../src/cli/onboarding.js";
 
 const arg = process.argv[2];
 if (arg === "--help" || arg === "-h") {
@@ -24,7 +24,7 @@ if (arg === "--version") {
   process.exit(0);
 }
 
-runOnboarding().catch((e) => {
+runScanWizard().catch((e) => {
   console.error(e.message);
   process.exit(2);
 });