# zzop [Health: Active] **Category:** πŸ’» Developer Tools **Repository:** https://github.com/eezz4/zzop **GitHub Stars:** 2 **Views:** 0 **Installs:** 0 **Upvotes:** 0 **Directory Page:** https://allmcps.com/mcp/zzop ## Description Deterministic cross-repo contract analysis for AI agents: frontend calls vs backend endpoints. ## Claude Desktop Quick Installation Heuristic fallback β€” verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low): ```json "mcpServers": { "zzop": { "command": "npx", "args": ["-y","zzop"] } } ``` ## Documentation & README # zzop ( Zero Zone Of Pain ) [![CI](https://github.com/eezz4/zzop/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/eezz4/zzop/actions/workflows/ci.yml) [![npm](https://img.shields.io/npm/v/@zzop/cli?logo=npm)](https://www.npmjs.com/package/@zzop/cli) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](./LICENSE) **Your AI coding agent can't read your whole codebase. zzop reads it β€” and answers the same way every time.** Point zzop at one repository, or at your frontend and backend together, and it returns a single JSON document describing what is actually there: which frontend calls reach which backend routes and which reach nothing, what looks risky, what is dead, where to refactor first β€” and what this run could not see. An agent starts from that instead of guessing from the handful of files it had room to open. zzop does not write code. It makes the *understanding* a code generator works from accurate and repeatable β€” same commit in, byte-identical findings out β€” so what your agent writes rests on what your code does rather than on what it inferred from a partial read. The thing being improved is comprehension, not capability. ## See it break something **[Break a route](https://github.com/eezz4/zzop/blob/HEAD/docs/demo/break-a-route.md)** is the whole product in one change: rename one backend route in a frontend/backend pair that share no code and no types. The frontend still compiles, its tests still pass β€” and zzop names both ends of the break, file and line (abridged here; the demo page shows the run's own format): ``` === unprovided consumes === "PUT /api/user" @ fe-vite src/pages/Settings.jsx:19 ← the call now hits nothing === unconsumed provides === "PUT /api/users/me" @ be-express src/app/routes/auth/auth.controller.ts:61 ← the route nobody calls ``` That page is a **narrated walkthrough**: every command and the output it produced are written out, so it reads end to end without you running anything. The script behind it, `docs/demo/break-a-route.sh`, is a maintainer tool rather than a first-run command β€” it builds a `cargo` example (so it needs a **source checkout**, not a released binary) and analyzes two repositories **you supply** at `corpus/oss/fe-vite` and `corpus/oss/be-express`. `corpus/oss/` is gitignored and nothing in this repo ships those trees β€” they are third-party checkouts, not ours to redistribute; see [CONTRIBUTING.md](https://github.com/eezz4/zzop/blob/HEAD/CONTRIBUTING.md) on bringing your own corpus. (The synthetic corpus we *did* write is committed, at [`cases/`](https://github.com/eezz4/zzop/blob/HEAD/cases/README.md) β€” every file of it but one, a fixture that has to carry a live vendor-token literal and so cannot be committed at all; its README says what that costs the benchmark score.) ## Which of the two binaries do you want? zzop ships as two Node-free binaries. Decide which one you need before you install anything: | If you want | Use | How you drive it | |---|---|---| | An AI agent (Claude Code, Claude Desktop, any MCP client) to answer questions about your repos | **`zzop-mcp`** β€” an MCP server over stdio | Install the plugin or the `.mcpb` bundle and the agent calls the tools. You run no commands. β†’ [Use in Claude Code](#use-in-claude-code-mcp-plugin) | | To run analyses yourself β€” a terminal, a CI job, a script | **`zzop`** β€” a plain CLI | `zzop init` once per tree, then `zzop analyze .` or `zzop cross --config …`. JSON to stdout. β†’ [Use in a terminal or CI](#use-in-a-terminal-or-ci-zzop-cli) | Both binaries dispatch to the same shared handlers over the same engine, so a tool call and a CLI run against the same path give the identical answer. Neither one makes a network request of any kind β€” they carry no HTTP dependency at all ([privacy](https://eezz4.github.io/zzop/privacy.html)). - Documentation site: (authored in [`site-src/`](https://github.com/eezz4/zzop/blob/HEAD/site-src/), generated by `scripts/gen-site.mjs`; [`site/`](https://github.com/eezz4/zzop/blob/HEAD/site/) is the committed output β€” a guard rejects hand edits to it) - Documentation (in-repo): [`docs/README.md`](https://github.com/eezz4/zzop/blob/HEAD/docs/README.md) - How it works, in depth: [`docs/ARCHITECTURE.md`](https://github.com/eezz4/zzop/blob/HEAD/docs/ARCHITECTURE.md) - External parser protocol: [`docs/NORMALIZED_AST.md`](https://github.com/eezz4/zzop/blob/HEAD/docs/NORMALIZED_AST.md) ## Quick start Neither binary needs Node.js, npm, or a compiler. Get them one of four ways: - **Download the binaries.** Grab the `zzop-cli-[.exe]` (CLI) and/or `zzop-mcp-[.exe]` (MCP server) assets for your platform from [GitHub Releases](https://github.com/eezz4/zzop/releases) and run them directly, or put them on `PATH`. Each release also carries a `SHA256SUMS` asset covering every one of those assets β€” **from v0.30.0 onward**; releases up to and including v0.29.1 do not have one, so on an older pin check that the file is there before relying on it. Verify with `sha256sum -c SHA256SUMS --ignore-missing`, or `shasum -a 256 -c SHA256SUMS --ignore-missing` on a macOS box that has no `sha256sum`. Its scope is narrow and worth stating: it catches a corrupted download, and it is a hook for anyone who obtained the digest through another channel. It does **not** defend against a compromised release origin β€” an attacker who can swap an asset can swap `SHA256SUMS` beside it β€” and TLS already refuses MITM. - **Claude Code plugin.** `/plugin marketplace add eezz4/zzop`, then `/plugin install zzop@zzop` β€” see [Use in Claude Code](#use-in-claude-code-mcp-plugin) below. (Windows: the install hook needs a POSIX shell β€” Git for Windows is the supported path; details in [packages/README.md](https://github.com/eezz4/zzop/blob/HEAD/packages/README.md#install-as-a-claude-code-plugin).) - **Claude Desktop.** One-click `.mcpb` bundle (drag-and-drop install) β€” what an installer should know BEFORE installing (updates are manual; on macOS the unsigned binary is expected to hit Gatekeeper; the privacy statement) is [packages/mcpb/BUNDLE-README.md](https://github.com/eezz4/zzop/blob/HEAD/packages/mcpb/BUNDLE-README.md) β€” bundles from releases after v0.32.0 carry that file as their own README; bundles up to and including v0.32.0 ship without it, which is exactly why the pre-install pointer here matters. Packaging internals: [packages/mcpb/README.md](https://github.com/eezz4/zzop/blob/HEAD/packages/mcpb/README.md). - **npm.** `npm i -g @zzop/cli` installs the exact same `zzop` binary above, fetched for your platform as an npm dependency β€” every subcommand `zzop help` lists, byte-for-byte the same output, no Node runtime involved beyond a tiny launcher script and no separate JS implementation that could drift from the native binary. Convenient when a project already manages its toolchain through npm. See [packages/cli/README.md](https://github.com/eezz4/zzop/blob/HEAD/packages/cli/README.md). ## Use in Claude Code (MCP plugin) The agent-facing lane. `zzop-mcp` is a self-contained binary with an MCP server built in; you install it once and then ask questions in plain language β€” the agent picks the tool. 1. `/plugin marketplace add eezz4/zzop` β€” then `/plugin install zzop@zzop` (two separate steps). 2. Start a new session. The plugin downloads the binary for your platform on first run; nothing goes on `PATH`. **That first session does not list the zzop tools yet** β€” the tool list is settled before the download finishes β€” so restart Claude Code once and they appear (the hook says so on stdout too). Once installed, a newer release is reported to you, never installed behind your back. The server exposes the tools `analyze_repo`, `cross_repo`, `check_file`, `check_endpoint`, `analyze_envelope`, `validate_envelope`, `validate_rule_pack` β€” plus the `zzop://contract/*` resources carrying the authoring contracts (among them the envelope schema, the DSL reference, the rule catalog, the config surface and an annotated starter config), so an adapter or rule pack can be written with nothing but the binary. `zzop-mcp` itself takes no analysis subcommands: bare or `mcp` serves stdio, and `version`/`help` are the only other forms. See [packages/README.md](https://github.com/eezz4/zzop/blob/HEAD/packages/README.md) for the full install/tool/resource reference, and [docs/modules/mcp.md](https://github.com/eezz4/zzop/blob/HEAD/docs/modules/mcp.md) for exact argument shapes. ## Use in a terminal or CI (`zzop` CLI) The human-facing lane. Write a `zzop.config.jsonc` and run it, ESLint-style. **A config is required** β€” every analysis lane refuses a tree that has none, on both binaries alike, because the names zzop would otherwise guess about your project (what you call your auth guards, which banners mark your generated files) live in that file, and a key you do not declare is a judgment zzop does not make: ```sh zzop init # write the starter config β€” do this first, once per tree zzop analyze . # analyze one repo/tree -> JSON findings summary zzop analyze --config ci/zzop.config.jsonc # same, for a config that does not sit at the tree root zzop analyze . --severity critical --limit 10 # narrow the findings LIST (counts always cover everything) zzop cross --config zzop.config.jsonc # cross-layer join, driven by that config zzop analyze . --fail-on critical # THE CI GATE: exit 3 when anything at/above that severity exists zzop --help # that one subcommand's own line (exit 0); `zzop help` prints them all ``` `zzop --help` is the canonical subcommand list β€” this README does not repeat it. **The exit code is `0` unless you ask otherwise.** Without `--fail-on`, a run answers only "did zzop run", so a tree full of criticals still exits `0`; with it, findings at or above the named severity exit `3` (a third code, so a CI log can tell a broken config on `1` apart from a real finding) while the whole reply still goes to stdout. Check what your build does rather than this paragraph: `zzop analyze . --fail-on critical; echo $?`. The full code table, including the `2` a provably unmatchable `--rule` id lands on, is in [docs/getting-started.md](https://github.com/eezz4/zzop/blob/HEAD/docs/getting-started.md#reading-the-output). **A run writes into the tree it analyzes.** The first analysis creates `.zzop/cache/` beside your config (the default `cacheDir`) and keeps the per-file analysis cache there β€” pure derived state, safe to delete, regenerated on the next run, and it grows with the tree rather than staying small (measure yours with `du -sh .zzop`; this repository's own is not a number worth printing here because it moves with every run). `zzop init` adds the anchored `**/.zzop/` line to that directory's `.gitignore` for you; set `"cacheDir": null` to write nothing at all. To track contract drift over time rather than at one instant, commit a **structural manifest** and diff a later run against it β€” the same shape a lint baseline file has, kept by you, not by zzop: ```sh zzop manifest ./api ./web > contracts.json # identity only: provides/edges/bucket membership zzop diff contracts.json contracts.new.json # read `transitions` first β€” a key that left `edges` # for `unprovidedConsumes` is a broken contract zzop facts ./api ./web > facts.json # post-assembly facts (per-tree CommonIr + the whole join, # uncapped) for your own rule program zzop graph ./api ./web > join.mmd # the cross-layer join as mermaid, for any renderer β€” # scoped with --scope/--top, every cap disclosed in the file zzop graph . --domain dep > imports.mmd # the FILE import graph instead β€” cycles drawn as hexagons # with thick arrows, from the engine's own circular findings zzop graph . --domain risk > risk.mmd # blast-radius hubs + extraction seams. The health SCORES # are NOT drawn β€” a table of numbers is not a graph zzop graph . --domain posture # the mutating attack surface and its guard status β€” # a box means GUARDED-OR-EXEMPT, never proven guarded zzop graph . --domain cochange > churn.mmd # which files keep changing TOGETHER, from git history β€” # not imports, so it finds the coupling no dep graph can see zzop graph . --domain dep --fold 2 # the SAME import graph with each path's first 2 segments # drawn as one box β€” the module map you were trying to see # IS the picture, and every edge says how many file edges # it collapsed. --fold 1 for the top-level view ``` The manifest is deliberately uncapped and carries no file or line, so a pure refactor diffs empty while a route leaving the join cannot hide above a summary's caps. `diff` refuses two manifests from different zzop builds unless you pass `--allow-tool-drift` (which then discloses the drift), and tags a removal attributable to a source that lost coverage as `blindnessSuspect` rather than calling it a deletion. `facts` is the other uncapped lane, and the consumer half of the custom-rule extension point: when the DSL cannot express your rule, zzop emits everything it knows after assembly and the cross-layer join β€” each tree's whole `CommonIr` plus every join bucket, verbatim β€” and your own program decides what counts as a problem. zzop neither runs your program nor reads its findings back; see [docs/modules/facade.md](https://github.com/eezz4/zzop/blob/HEAD/docs/modules/facade.md#custom-rules-consumer-side-zzop-facts) for the shape. `manifest`, `diff`, `facts`, `coverage`, `graph`, `explain` and `init` are CLI-only lanes with no MCP tool twin. The rest of the surface: `analyze-envelope`, `validate-envelope`, `validate-rule-pack`, `endpoint`, `file` (everything zzop knows about ONE file β€” its tree, symbols, io facts, dependency edges both ways, and every finding anchored there; its verdict says whether the file was ANALYZED, so an empty findings list is never mistaken for "clean" on a file nothing structural ran on), `init` (write the annotated starter `zzop.config.jsonc`; the same document MCP serves as the `config-template` resource), `contract`, `explain`, `version`, `help`. See [packages/README.md](https://github.com/eezz4/zzop/blob/HEAD/packages/README.md) for the full CLI and config reference. To embed the engine instead of running either binary, call the `zzop-facade`/`zzop-summary` crates' JSON-in/JSON-out contract directly β€” they are workspace-internal and not published to crates.io, so an in-process Rust dependency means vendoring this workspace, not `cargo add`. Shelling out to the CLI's JSON subcommands needs no linkage at all: ```rust let report: serde_json::Value = serde_json::from_str(&zzop_facade::analyze_json(r#"{"root":"."}"#)?)?; ``` ## Result (abridged) This is what the two binaries above actually print β€” `findings` is a **census object**, not an array, because the reply is a shaped summary rather than a raw dump. The numbers below are a real run against this repository's own `cases/trees/api-be` fixture, **measured with a `zzop` built from this checkout**: `zzop analyze --config cases/trees/api-be/zzop.config.jsonc`. **Which binary you reproduce them with is part of the claim.** `zzop version` prints the release number alone, and `main` keeps that number between releases β€” so an installed `@zzop/cli` and a build of this checkout can both answer `0.33.0` and legitimately report different findings, because they are different builds of one version string. `zzop version --verbose` is what tells them apart: it prints each parser's fingerprint and the engine hash. If your counts differ from the block below, compare that line before assuming either side is wrong. (To the next editor: these numbers move whenever `cases/trees/api-be` changes **and whenever a release changes what is measured** β€” re-run that command and re-measure them, never patch one in isolation. Three of them were stale for exactly that second reason until 2026-08-11 β€” and the whole block was again on 2026-08-15, after v0.31.0 exported the `code-hygiene` pack out of the bundle and 114 findings became 85. It happened a THIRD time on 2026-08-21, and that time nothing about the fixture moved: a Prisma delegate-accessor fix changed what `schema/unreferenced-field-name` counts as referenced, one info finding went away, and 85 became 84 with this block untouched. The lesson the first two did not teach is in this paragraph's first sentence β€” "whenever a release changes what is measured" includes every rule change, not only the loud ones, and no guard here can catch it, because the only machine that knows the number is the run. An outside reader reported 87/73 for this block on the same day and was NOT reading a stale README: they measured with the published `@zzop/cli` 0.33.0, a different BUILD of the same version string, and got a legitimately different answer. That is what the paragraph above this one is for. The `disclosure` line below is deliberately no longer one of these numbers: see its own comment.) `pain` never travels alone. `painMeasuredWeight` / `painTotalWeight` is how much of the weight table this tree could actually be measured on, and `pain: null` means no metric had a population at all β€” absence of data, never a clean bill. **And `pain` is not a defect score.** It contains no rule findings whatever: the run below reports 84 findings, 5 of them critical, while its `defect` pain is `0`. `painByAxis` splits the number so that is visible instead of implied β€” `defect` (import cycles, the only entry), `opinion` (barrel discipline, FSD layering, SDP/Main Sequence, Newman modularity, LOC ceilings β€” a project that deliberately does the opposite is not wrong, it scores low), and `history` (rename churn, bus factor). The three sit on `pain`'s own scale and sum to it. Read `findings` for defects; read `pain` for how much zzop disagrees with how the code is arranged. ```json { "fileCount": 84, "findings": { "total": 84, "bySeverity": { "critical": 5, "warning": 71, "info": 8 }, "byRule": { "security/weak-crypto": 6, "db/unawaited-write": 1 }, "shown": [ /* 50 here β€” the listed slice, capped by --limit; each entry has ruleId, severity, file, line, message */ ] }, "architecture": { "pain": 7.5, "painMeasuredWeight": 13.8, "painTotalWeight": 18.6, "painByAxis": [ { "axis": "defect", "pain": 0.0, "totalWeight": 3.0 }, { "axis": "opinion", "pain": 7.5, "totalWeight": 15.0 }, { "axis": "history", "pain": 0.0, "totalWeight": 0.6 } ], "topRecommendation": null, "criticalTop": [], /* + painMeaning / topRecommendationMeaning / criticalTopMeaning: the sentences that say what each of the three above is, and is NOT, on the wire */ }, "coverage": { /* how much of the tree zzop actually saw, per extension */ }, "coverageGaps": { /* which principal extensions reached no resolved import edge, always present β€” each row's `kind` ("source" vs "data-config") is what says whether the zero means a missing parser or a filetype you have to open to judge */ }, "disclosure": { /* the census of zzop's OWN known silent-failure classes, keyed classes / asserted / partial / notYetDetected, plus the `note`, `command` and `resource` that lead to the full text. No counts are copied here: the reply carries its own, and the two that were copied here went stale while the two beside them stayed right β€” which is indistinguishable from correct until someone re-runs it. Read them with `zzop contract disclosure-classes`, the command the field itself names. */ }, "warnings": [ /* anything this run could not provide */ ] } ``` Every finding carries a rule id, severity, a `file:line` location, and a message naming the config key that silences it β€” the records themselves ride in `shown`. `bySeverity`/`byRule` always count the WHOLE run, so a `--limit` that shortens that list never changes them; that split is why `findings` is an object. The per-metric `scores` block, the `health` object and `recommendations` are **not** on this wire: the shaped summary folds them into the compact `architecture` object above. They exist in full only in the `zzop-facade` embedding lane (`zzop_facade::analyze_json`, the snippet just above) β€” see [docs/modules/facade.md](https://github.com/eezz4/zzop/blob/HEAD/docs/modules/facade.md) for that lane's own shape. `analyzeTrees` (multi-tree) additionally returns `crossLayerFindings` β€” frontend fetch <-> backend route joins β€” which has no single-tree equivalent. ## How it works Each repository is parsed into one language-neutral IR, so a Python route and a TypeScript `fetch` end up as the same kind of fact. The headline move is the cross-repo join: frontend calls are exact-matched against backend routes across the repo boundary, and the leftovers are named rather than dropped β€” a casing or base-path difference, a version drift, a method mismatch each come back as a near-miss finding naming the dimension that differs, instead of a diff you have to do by hand. A near miss is judged on those axes, never on spelling: a plural or a typo (`/api/userss` against `/api/users`) is reported as an unmatched call, not paired with the route it probably meant β€” the per-rule scope is in [the catalog](https://github.com/eezz4/zzop/blob/HEAD/docs/rules/catalog.md). Alongside the join, the same engine runs a layered rule system (native whole-graph analyses plus declarative JSON rule packs) over each repo individually, adding structural findings, dependency/dead-code analysis, and health scores to the same JSON document. Every run is deterministic β€” same code in, same findings out, byte-stable enough to diff two runs against each other. That is what makes zzop usable as a CI gate (fail a PR on contract drift by reading the JSON severity counts) and as a substrate an agent can re-run without chasing a moving answer. Just as important, a run reports its own blind spots: `warnings` and the per-tree `coverage` census say what did **not** run, so a short findings list can be told apart from a blind engine. Full design: [`docs/ARCHITECTURE.md`](https://github.com/eezz4/zzop/blob/HEAD/docs/ARCHITECTURE.md). Reading the output, severity semantics and suppression: [`docs/getting-started.md`](https://github.com/eezz4/zzop/blob/HEAD/docs/getting-started.md). When your stack does not match the defaults β€” a house extension, your own guard names, a gateway prefix, a rule that does not exist yet β€” [`docs/extending.md`](https://github.com/eezz4/zzop/blob/HEAD/docs/extending.md) lists every plug-in point in the order you hit them. ## Supported languages | Language | Support | |---|---| | TypeScript / JavaScript (`.ts, .tsx, .js, .jsx, .mjs, .cjs, .mts, .cts`) | Native, full AST (swc): symbols, imports, calls, HTTP routes/egress, TypeORM `@Entity`/`@Column` `db-table` **provides** (the schema side, joining the client-side consumes), `db-table` consumes from ORM accessors AND from raw SQL statement strings | | Python (`.py, .pyi`) | Native, full AST (ruff, Python 3 β€” Python-2-only syntax falls back to lexical): symbols, imports, FastAPI route provides, Django URLconf route provides (`urlpatterns` `url()`/`re_path()`/`path()` entries with cross-file `include('')` mounts, emitted verb-unknown since the method lives in the view class), `requests`/`httpx` consumes (module-level calls plus `Session`/`Client`/`AsyncClient` instances), SQLModel/SQLAlchemy + Django ORM `db-table` provides and their query-site consumes, call sites, auth-guard evidence (FastAPI `Depends` + DRF `permission_classes`) β€” v1 scope | | Rust (`.rs`) | Native, full AST (syn 2): symbols, imports/`mod` tree (incl. same-workspace crate resolution), axum route provides, `reqwest` consumes, raw-SQL `db-table` consumes (sqlx/tokio-postgres/rusqlite/…), call sites for the whole-repo call graph, extractor-based auth-guard evidence β€” v1 scope | | Go (`.go`) | Native, full CST (tree-sitter-go 0.25): symbols, imports/dep graph (`go.mod` module resolution, package-directory-wide edges), gin + `net/http` route provides (cross-file mount composition β€” a function-parameter router mounted from another file's call site β€” incl. Go 1.22 `"METHOD /path"` mux syntax), `net/http` literal egress consumes (package free functions plus bound `http.Client` values), GORM `db-table` facts, call sites β€” v1 scope | | Java (`.java`) | Native, full CST (tree-sitter-java 0.23.5, Java 21 grammar): symbols (incl. nested types, dot-qualified method names, real visibility), imports/dep graph (`(package, type)`-indexed resolution, glob package-directory-wide edges), Spring MVC route provides (cross-file `extends`-chain + constant-prefix resolution), `RestTemplate`/`WebClient` literal egress consumes (Feign and `java.net.http` not recognized; `RestTemplate.put`/`.delete` deliberately not recognized, generic names that would false-key `Map.put` β€” disclosed), JPA `@Entity`/`@Table` `db-table` provides, call sites, Spring Security auth-guard evidence (`@PreAuthorize`/`@PostAuthorize`/`@Secured`/`@RolesAllowed`) β€” v1 scope | | C# (`.cs`) | Native, full CST (tree-sitter-c-sharp 0.23.5): symbols (incl. nested types, dot-qualified method names, `public` visibility), imports/dep graph (namespaceβ†’files index, `using` package-directory-wide edges), ASP.NET Core route provides (attribute controllers with `[Route("api/[controller]")]` + `[HttpGet]`/… composition, plus same-file Minimal-API `app.MapGet`/`MapGroup`), `HttpClient` literal egress consumes, EF Core `DbSet`/`[Table]` `db-table` provides, call sites β€” v1 scope | | Prisma schema (`.prisma`) | Native, lexical schema: models/fields (structural + usage-aware schema rules) + `db-table` provides joining the client-side consumes | | SQL (`.sql`) | Native, lexical: `CREATE TABLE` β†’ `db-table` provides (migration files light up the db-table channel for MyBatis/JDBC-style stacks). The crate also owns the channel's consume-side statement reader, which other parsers call on the SQL strings they hold | | Anything else (Ruby, JSP, ...) | Lexical fallback in-tree: the files are walked and counted, and only `line-scan` rules can reach them. **That is a ceiling, not a promise of coverage** β€” a bundled rule reaches your language only if its own `file_pattern` names the extension, and for most languages outside the rows above none does, which is a zero this row deliberately does not spell as a number (it is per-language and it moves). Measure it on YOUR tree instead: `zzop analyze ` and read `packsLoaded[].filesInScope` β€” `0` on a pack means not one of its rules' path gates admits a byte here, so that pack's zero findings are scope, never a clean bill β€” beside `coverageGaps`, whose row for the extension carries `kind: "source"`. Measured that way on a five-file Ruby tree, no bundled pack admitted a single `.rb` file. First-class support is an external parser adapter conforming to the [Normalized AST protocol](https://github.com/eezz4/zzop/blob/HEAD/docs/NORMALIZED_AST.md). | Full precision-tier breakdown β€” exactly what each native parser extracts, Python's v1 scope note, and each parser's fingerprint β€” in [docs/ARCHITECTURE.md](https://github.com/eezz4/zzop/blob/HEAD/docs/ARCHITECTURE.md#language-support). (Those fingerprints are not in `zzop version`'s default output, which prints the bare release number so scripts can parse one token; `zzop version --verbose` β€” and `zzop-mcp version --verbose`, the identical string β€” prints them, and `zzop manifest`'s `tool` field carries the same string inside the artifact.) Rust carries one reporting rule no other language has: a finding whose line sits inside a `#[cfg(test)]`/`#[test]`-gated item is dropped, because Rust's unit tests live inside the shipping file where the path-shaped test exclusion every other language relies on (`foo.test.ts`, `tests/test_foo.py`) cannot see them. The credential-at-rest rules opt out and keep judging those regions β€” a committed key is leaked whether or not the compiler keeps it β€” and each says so in its own catalog row. Both halves: [docs/rules/catalog.md](https://github.com/eezz4/zzop/blob/HEAD/docs/rules/catalog.md). A normal-sized file whose extension has no native parser also self-reports in the output's `warnings` β€” naming the extension, a file count, and a path sample β€” instead of vanishing silently; point it at an adapter (`overlays: [...]` in `zzop.config.jsonc`) if that language matters for the analysis. ## Versioning & stability zzop is **pre-1.0 (`0.x`) and unstable** β€” any release may change behavior, output, rules, or defaults, so pin an exact version (not a `^`/`~` range) and re-test before upgrading. Semantic Versioning begins at `1.0.0`. What is promised before then is narrower, and is a promise about the record rather than the rate: a break to one of the surfaces [VERSIONING.md](https://github.com/eezz4/zzop/blob/HEAD/VERSIONING.md) names is written down, old and new spelling both, in [CHANGELOG.md](https://github.com/eezz4/zzop/blob/HEAD/CHANGELOG.md). VERSIONING.md is also where the properties *inside* those surfaces that are still moving get named β€” rule ids, `SourceSymbol.id` uniqueness, native id namespaces β€” rather than left for you to infer from a run. ## Layout & development Contributing, or just want the crate map? [`CONTRIBUTING.md`](https://github.com/eezz4/zzop/blob/HEAD/CONTRIBUTING.md) carries both β€” the per-crate responsibility list and the build/test/measure commands. They live there rather than here because this page is read to DECIDE whether to adopt zzop, and a dependency graph answers a question nobody asks before installing. ## License MIT β€” see [`LICENSE`](https://github.com/eezz4/zzop/blob/HEAD/LICENSE).