Hokmah

Estimates the impact of a described code change on an imported public GitHub repository. `repo_url` is https://github.com/<owner>/<repository> and `query` describes the change in plain language; `branch` is accepted for compatibility, the analysis uses the history imported from the default branch. Returns a risk assessment with the files, symbols and modules likely to be affected and related commits, computed from the repository graph without a language model.

Ranks 2 to 8 zones of an imported repository from the one that works worst to the one that works best, with the reasons: fixes per feature, fixes per 1000 lines and tests, over the last 12 months. Each zone is a path prefix or a few words.

Imports a public GitHub repository so it can be analyzed: indexes its source files (.py .js .ts .jsx .tsx .vue .mjs .mts .rs .go .java) and its latest commits (up to 500) from the default branch into a dependency and change-history graph. `repo_url` is https://github.com/<owner>/<repository>; `branch` is accepted for compatibility. A repository already imported is not imported again. Returns the project id and the number of commits and files ingested.

Overview of an imported repository: the most fragile areas (fixes per feature over 12 months), the fastest growing and the new ones, the busiest, the largest files, the most co-changed files, and how many internal imports could be resolved.

Lists current code of an imported repository that lacks a protection the project's own fixes keep adding, learned from the diffs of its past fixes: unguarded access to structures fixes had to guard, including an entry checked to exist but read at [0] without checking it has an element, or passed to a function that dereferences it (R1); results of functions that fixes had to null-check, called the way the fixes checked them and declared nullable, used unchecked (R7); plain objects used as dictionaries keyed by request input and written through the looked-up value, obj[k].x = v (R2, prototype pollution; a one-level write is only a hardening note); template variables inserted unescaped where another file sanitizes them (R3). Optional `zone` (path prefix or words) and `kind` (R1, R2, R3, R7). kind="UI" lists the interface instead: translation keys missing from the base locale or called without the values their text needs (U1), screens that await a request on opening without handling its failure (U4), and, not validated on history, accessibility notes (U5). Each site says why it was flagged; `measured_on_history` gives, per kind, how often such sites turned out to need a fix when the detectors were run on the code of a year earlier. Candidates are not confirmed bugs.

Architecture seams of an imported repository: a DISTINCT axis from risk — not "where is the code fragile?" but "where does the code fight its own structure?". A seam is a source of truth split across module boundaries: files in different packages that keep being edited together over the history (e.g. the same list enumerated in two packages). Read from the co-change history alone, scored by near-inseparability (jaccard) with a hub penalty, so wanted shared contracts (api-types/dto/schema...) are listed apart, never counted as debt. Each seam carries its evidence (shared identifiers, co-commits, span) and a confidence; the tool proposes, it does not decide — a seam is not a bug and never appears in the risk axis. `scope` = actionable (default) | all | expected; `min_jaccard` filters weaker seams; `zone` (path prefix or words) narrows to seams touching that zone. Backed by a retrospective bench (backtest_coupling): on the reference repo a flagged seam predicts future co-change with a lift of several times over a random previously-coupled pair.

Finds past fixes of a kind of bug ("null run data guard", "prototype pollution", "race condition on resume") in an imported repository, and the current files where the same defect may still exist: files of the same kind next to the fixed ones, files that usually change with them but were left out, and files that contain the identifiers the fix changed. Read each candidate with the fix in mind; a candidate is not a confirmed bug.

Says how well a part of an imported repository is doing and what to do about it. `zone` is a path prefix (packages/cli/src/webhooks) or a few words ("MFA recovery codes"). Returns, from the last 12 months of history and the current code: a verdict (stable, active, growing, maintenance, fragile), fixes per feature and per 1000 lines, the recurring fix themes specific to the zone, giant files and functions, files often changed without tests, coupled areas, parallel implementations, and recommendations with the numbers behind each one. No language model is involved.