Fallow
NPM · FALLOW
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
Available components
Last scanned (14 hours ago)
Scores higher than 73% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 9 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to fallow-rs/fallow). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 31281 tokens (~601/item across 52 items; 44 tools + 8 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "check_runtime_coverage" implies "merge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 46 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
- Package version: 3.44.0 → 3.45.0 functional
- 19 Nov 26 0
- Package version: 3.43.2 → 3.44.0 functional
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 3.43.1 → 3.43.2 functional
- 15 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Nov 26 +1
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Package version: 3.43.0 → 3.43.1 functional
- 13 Nov 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/fallow@3.45.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | fallow-rs/fallow |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/fallow-rs/fallow/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 4021475898 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2899e538157f6b770361a7e73bcfdda92b440c04503e22f547eeb9250da5f6efabf6c832b7424d35b0cad09d73b195a783eed242fba479a9ee3619f42 |
Background: How many MCP packages publish verified provenance →
Dependencies 9 packages
| Packages resolved | 9 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze ~1,379
Analyze a TypeScript/JavaScript project for unused code and dependency cycles. On a Rust root, it runs `cargo fallow check` (deps, visibility; no score) and takes only root. Detects unused files, exports, types, dependencies, enum/class members, unresolved imports, unlisted dependencies, duplicate exports, circular dependencies, re-export cycles (barrel files that form a structural loop, silently breaking re-exports), package cycles (workspace packages that import each other in a loop), boundary violations, rule-pack policy violations (banned calls, imports, and catalogue-derived effects declared via the rulePacks config key), stale suppression comments, missing suppression reasons when rules.require-suppression-reason is enabled, unused pnpm catalog entries (entries in pnpm-workspace.yaml `catalog:` / `catalogs:` not referenced by any workspace package), empty pnpm catalog groups, unresolved catalog references (workspace package.json declares `catalog:` but the catalog has no entry), unused dependency overrides (entries in `pnpm-workspace.yaml#overrides`, `package.json#pnpm.overrides`, top-level `package.json#overrides`, or Bun `package.json#resolutions` whose target package no workspace package declares and the active readable lockfile does not resolve), and misconfigured dependency overrides (unparsable key or empty value; the active package manager may reject or ignore the entry). Opt-in issue_types: ["private-type-leaks"] (API hygiene), ["deprecated-exports-in-use"] (@deprecated in use), ["absent-component-props"] (optional-prop review), ["constant-parameters"] (parameter review). Returns structured JSON with all issues found, grouped by issue type. Each finding has a stable `finding_id`; an id absent from a scoped or differently configured run means unknown, not resolved. For code duplication use find_dupes, for complexity hotspots use check_health. Supports baselines, regression detection, performance tuning, boundary_violations, and group_by. Read the `fall…
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| baseline | string|null | – | Compare results against a saved baseline file. Only new issues (not in the baseline) are reported. The response carries `baseline_staleness`: read `gate_trips` to see whether the baseline has entries… |
| boundary_violations | boolean|null | – | Analyze only architecture boundary violations. |
| config | string|null | – | Path to a fallow config file. |
| fail_on_regression | boolean|null | – | Fail if the issue count increased beyond `tolerance` compared to a regression baseline. |
| file | array|null | – | Scope analysis to these project-relative files instead of the whole project. |
| finding_ids | array|null | – | Report only these `finding_id` values. The response adds `finding_id_query`; a missing id is resolved only when `conclusive` is true. |
| group_by | string|null | – | Group findings by CODEOWNERS ownership, directory, workspace package, or GitLab CODEOWNERS section. Values: "owner", "directory", "package", "section". |
| include_entry_exports | boolean|null | – | Report unused exports in entry files instead of auto-marking them as used. |
| issue_types | array|null | – | Issue types to include, for example `["unused-exports", "unused-files"]`; empty or omitted means all registered issue types. |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| no_package_baselines | boolean|null | – | Ignore the per-package refs of `workspaces.changedSince` for this call, so every workspace package is analyzed in full scope. Use it to judge or save a whole-project baseline. |
| production | boolean|null | – | Production mode: exclude test, story, and dev files, only start/build scripts, and report type-only dependencies. |
| regression_baseline | string|null | – | Path to the regression baseline file. |
| root | string|null | – | Project root; defaults to the working directory. |
| save_baseline | string|null | – | Save current results as a baseline file for future comparisons. The path must resolve inside the project root, its Git work tree, the CI workspace or a temp directory. A relative path resolves agains… |
| save_regression_baseline | string|null | – | Save the current issue counts as a regression baseline file at this path. An empty or absent value writes nothing: this tool cannot write the counts into the fallow config. The path must resolve insi… |
| show_cascade | boolean|null | – | Keep the unused exports, types, class members and enum members of unused files. By default the report hides them and counts them in `cascade_hidden`. Passed through to the CLI's `--show-cascade` flag. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| tolerance | string|null | – | Allowed issue count increase before a regression is flagged. Defaults to "0". |
| type_aware | boolean|null | – | Refine project-wide public API findings with TypeScript symbol identity. `false` keeps the run syntactic, also when the config turns type-aware analysis on. `type_aware_projects` or `type_aware_requi… |
| type_aware_projects | array|null | – | Explicit tsconfig paths for type-aware analysis. |
| type_aware_require | – | – | Whether incomplete semantic evidence is advisory or gating. |
| workspace | string|null | – | Workspace packages to analyze: name or repo-relative path, comma-separated list, globs, `!` negation. |
No output schema declared.
No examples provided.
audit ~2,024
Audit changed files for dead code, complexity, duplication, styling, and diff risk. Purpose-built for reviewing AI-generated code. Combines the analyses scoped to changed files and returns a verdict (pass/warn/fail). Auto-detects the base branch if not specified. By default, audit runs the base ref too and gates only findings introduced by the changeset; inherited findings are annotated with introduced=false and counted under attribution. Set gate="all" or audit.gate="all" in config to gate every finding. Returns JSON with verdict, summary counts per category, attribution counts, and full issue details with actions array for remediation guidance. Per-analysis payloads nest under `dead_code`, `duplication`, and `complexity`; the `complexity` block carries the health sub-analysis output (audit JSON has no `health` key). The `diff_risk` section reports facts about the change itself, such as weakened tests, added suppressions, and a clone copy edited without its siblings. Styling analytics are on by default. Read the fallow://tools/audit guide for the diff-risk rules, styling, coverage, synthetic complexity units, grouping, baselines, runtime coverage, and `FALLOW_DIFF_FILE` scoping. Use this after generating code to verify quality before committing.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| base | string|null | – | Git ref to compare against (e.g., "main", "HEAD~5"). When unset, the base is the git merge-base against the branch's upstream or the remote default (`origin/main`); set `FALLOW_AUDIT_BASE` in the ser… |
| config | string|null | – | Path to a fallow config file. |
| coverage | string|null | – | Path to Istanbul coverage data (coverage-final.json) or raw V8 coverage (a `NODE_V8_COVERAGE` directory or one V8 JSON file) for accurate per-function CRAP scores in audit's health sub-analysis. When… |
| coverage_root | string|null | – | Absolute prefix to strip from coverage data paths before CRAP matching. Use when coverage was generated in a different checkout root in CI or Docker. When omitted, `FALLOW_COVERAGE_ROOT` and then the… |
| css | boolean|null | – | Set `false` to skip styling analytics in audit. Unset or `true` uses `audit.css` from the config, which defaults to enabled. |
| css_deep | boolean|null | – | Enable or disable deep CSS analysis for audit: project-wide styling reachability and near-duplicate theme-token candidates, narrowed back to changed anchors. Unset uses `audit.cssDeep` from the confi… |
| dead_code_baseline | string|null | – | Path to a dead-code baseline file (produced by `fallow dead-code --save-baseline`). When set, dead-code issues present in the baseline are excluded from the audit verdict. Passed through to the CLI's… |
| dupes_baseline | string|null | – | Path to a duplication baseline file (produced by `fallow dupes --save-baseline`). When set, clone groups present in the baseline are excluded from the audit verdict. Passed through to the CLI's `--du… |
| explain_skipped | boolean|null | – | Show per-pattern counts for skipped files: the default duplicates ignores, and the built-in discovery ignores that removed source files from the walk. Human-format only (human/markdown CLI output); M… |
| gate | string|null | – | Which findings affect the audit verdict. Values: "new-only" or "all". Unset uses `audit.gate` from the config, which defaults to "new-only". Passed through to the CLI's `--gate` flag. |
| group_by | string|null | – | Group audit findings by CODEOWNERS ownership, directory, workspace package, or GitLab CODEOWNERS section. Values: "owner", "directory", "package", "section". `section` attaches an `owners: string[]`… |
| health_baseline | string|null | – | Path to a health baseline file (produced by `fallow health --save-baseline`). When set, complexity findings present in the baseline are excluded from the audit verdict. Passed through to the CLI's `-… |
| health_baseline_mode | – | – | How `health_baseline` matches complexity findings: "count" (per file and category, the CLI default) or "identity" (per function identity, strict; requires a baseline saved with `--baseline-mode ident… |
| include_entry_exports | boolean|null | – | Report unused exports in entry files instead of auto-marking them as used. Catches typos in framework exports (e.g. `meatdata` instead of `metadata`). Also configurable persistently via `includeEntry… |
| max_crap | number|null | – | Maximum CRAP score threshold (default 30.0). Functions meeting or exceeding this score cause audit to fail. Pair with `coverage` on `check_health` for accurate per-function CRAP; without Istanbul dat… |
| min_invocations_hot | integer|null | – | Threshold for hot-path classification (default 100). Forwarded to the sidecar when `runtime_coverage` is set. Passed through to the CLI's `--min-invocations-hot` flag. |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| only | array|null | – | Run only these audit sub-analyses, with the values of bare `fallow --only`: `dead-code`, `architecture`, `dupes`, `health`. Replaces the `audit.deadCode`, `audit.health` and `audit.dupes` config sele… |
| production | boolean|null | – | Only analyze production code (excludes tests, stories, dev files). |
| production_dead_code | boolean|null | – | Run only the dead-code sub-analysis in production mode. |
| production_dupes | boolean|null | – | Run only the duplication sub-analysis in production mode. |
| production_health | boolean|null | – | Run only the health sub-analysis in production mode. |
| root | string|null | – | Project root; defaults to the working directory. |
| runtime_coverage | string|null | – | Runtime coverage input (V8 directory, V8 JSON, or Istanbul coverage map JSON). When set, audit adds runtime-coverage findings to the same call: agents get the `hot-path-touched` verdict next to dead-… |
| show_cascade | boolean|null | – | Keep the unused exports, types, class members and enum members of unused files. By default the report hides them and counts them in `cascade_hidden`. Passed through to the CLI's `--show-cascade` flag. |
| skip | array|null | – | Skip these audit sub-analyses, with the values of `only`. A skipped sub-analysis leaves the verdict; the response omits its block and sets `summary.dead_code_skipped`, `complexity_skipped` or `duplic… |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| type_aware | boolean|null | – | Refine both audit sides with TypeScript symbol identity before attribution. `false` keeps the run syntactic, also when the config turns type-aware analysis on. `type_aware_projects` or `type_aware_re… |
| type_aware_projects | array|null | – | Explicit tsconfig paths for type-aware analysis. |
| type_aware_require | – | – | Whether incomplete semantic evidence is advisory or gating. |
| workspace | string|null | – | Workspace packages to analyze: name or repo-relative path, comma-separated list, globs, `!` negation. |
| worsened | string|null | – | Verdict effect of an inherited complexity finding whose measured value grew: "warn" (default), "error" (counts as introduced) or "off". Unset uses `audit.worsened`. |
No output schema declared.
No examples provided.
check_architecture ~396
Check import cycles, boundary violations (with coverage and forbidden calls), and rule-pack policy violations. Returns the `kind: "architecture"` envelope: the finding arrays, `finding_id` values and actions of `analyze` for these issue types, with its own `schema_version`. Set `cycles`, `boundaries`, or `policy` to report one kind. Call `guard` before an edit and this tool after it. `baseline` takes a dead-code baseline. On a Rust root, it runs `cargo fallow boundaries`: `kind: "boundaries"`.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| baseline | string|null | – | Saved dead-code baseline file; only new findings are reported. |
| boundaries | boolean|null | – | Only boundary violations, coverage and forbidden calls. |
| changed_since | string|null | – | Report only findings in files changed since this git ref. |
| config | string|null | – | Path to a fallow config file. |
| cycles | boolean|null | – | Only import cycles. |
| file | array|null | – | Project-relative files to scope the report to. |
| group_by | string|null | – | "owner", "directory", "package", or "section". |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| policy | boolean|null | – | Only rule-pack policy violations. |
| production | boolean|null | – | Production mode: exclude test, story, and dev files, only start/build scripts, and report type-only dependencies. |
| root | string|null | – | Project root; defaults to the working directory. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| workspace | string|null | – | Workspace packages to analyze: name or repo-relative path, comma-separated list, globs, `!` negation. |
No output schema declared.
No examples provided.
check_changed ~767
Analyze only files changed since a git ref. Useful for incremental CI checks on pull requests. Returns the same structured JSON as analyze, but filtered to only include issues in changed files. Each finding keeps its `finding_id` from analyze; an id absent here means unknown, not resolved. Supports baseline comparisons (baseline/save_baseline), regression detection (fail_on_regression, tolerance, regression_baseline, save_regression_baseline), and performance tuning (no_cache, threads).
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| baseline | string|null | – | Compare results against a saved baseline file. Only new issues (not in the baseline) are reported. The response carries `baseline_staleness`: read `gate_trips` to see whether the baseline has entries… |
| config | string|null | – | Path to a fallow config file. |
| fail_on_regression | boolean|null | – | Fail if the issue count increased beyond `tolerance` compared to a regression baseline. |
| include_entry_exports | boolean|null | – | Report unused exports in entry files instead of auto-marking them as used. |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| production | boolean|null | – | Production mode: exclude test, story, and dev files, only start/build scripts, and report type-only dependencies. |
| regression_baseline | string|null | – | Path to the regression baseline file. |
| root | string|null | – | Project root; defaults to the working directory. |
| save_baseline | string|null | – | Save current results as a baseline file for future comparisons. The path must resolve inside the project root, its Git work tree, the CI workspace or a temp directory. A relative path resolves agains… |
| save_regression_baseline | string|null | – | Save the current issue counts as a regression baseline file at this path. An empty or absent value writes nothing: this tool cannot write the counts into the fallow config. The path must resolve insi… |
| show_cascade | boolean|null | – | Keep the unused exports, types, class members and enum members of unused files. By default the report hides them and counts them in `cascade_hidden`. Passed through to the CLI's `--show-cascade` flag. |
| since | string | yes | Git ref to compare against (e.g. "main", "HEAD~5"). Only files changed since this ref are analyzed. Required. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| tolerance | string|null | – | Allowed issue count increase before a regression is flagged. Defaults to "0". |
| workspace | string|null | – | Workspace packages to analyze: name or repo-relative path, comma-separated list, globs, `!` negation. |
No output schema declared.
No examples provided.
check_health ~3,718
Check code health metrics (cyclomatic and cognitive complexity) for functions in the project. Returns structured JSON with complexity scores per function, sorted by severity. On a Rust root, it runs `cargo fallow complexity` (max_cyclomatic, max_cognitive; no score). Set score=true for a single 0-100 health score with letter grade (A/B/C/D/F); runs duplication analysis automatically, but the churn-backed hotspot penalty requires hotspots=true (or targets=true). Set min_score=N to fail only when the score drops below a threshold (CI quality gate); min_score is authoritative, so complexity findings become informational and min_score=0 never fails. Exit codes are not surfaced over MCP, but the verdict is: a gated run publishes `gate_outcomes`, where `health-min-score` and `health-min-severity` carry a status, whether it was enforced, and the numbers compared. min_severity composes with min_score. Set file_scores=true for per-file health scores (maintainability index, fan-in, fan-out, dead code ratio, complexity density, CRAP risk), sorted in risk-aware triage order so lower MI and higher CRAP risk appear first. Set css=true to add a `css_analytics` section (specificity hotspots, `!important` density, over-complex selectors, deep nesting, design-token sprawl, unreferenced custom properties and `@keyframes`); opt-in because it parses every project stylesheet. Set complexity_breakdown=true to add a per-decision-point `contributions[]` array to each complexity finding, so you can explain WHY a function scored high and which lines to refactor. Set coverage_gaps=true to explicitly include static test coverage gaps: runtime files and exports with no test dependency path (not line-level coverage). A provided config file may also enable coverage gaps via rules.coverage-gaps when no health sections are explicitly selected. Set hotspots=true to identify files that are both complex and frequently changing (combines git churn with complexity). Set churn_file to a `fallow-churn/v1`…
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| baseline | string|null | – | Compare results against a saved baseline file. Only new issues (not in the baseline) are reported. `summary.baseline_staleness` reports how much of the baseline still matches: read `gate_trips` to se… |
| baseline_mode | – | – | How `baseline` matches health findings and which buckets `save_baseline` writes: "count" (per file and category, the CLI default) or "identity" (per function identity, strict; requires a baseline sav… |
| changed_since | string|null | – | Git ref to compare against. Only files changed since this ref are analyzed. |
| churn_file | string|null | – | Import change history from a `fallow-churn/v1` JSON file instead of `git log`, so `hotspots` / `ownership` / `targets` work on projects with no git repository (Yandex Arc, Mercurial, Perforce). A sma… |
| complexity | boolean|null | – | Show only complexity findings. By default all sections are shown; use this to select only complexity. |
| complexity_breakdown | boolean|null | – | Include the per-decision-point complexity breakdown (`contributions[]`) on each complexity finding. Each entry names the construct (if, else-if, Svelte await/then, loop, boolean operator, React hook… |
| config | string|null | – | Path to a fallow config file. |
| coverage | string|null | – | Path to coverage data for accurate per-function CRAP scores: an Istanbul map (coverage-final.json), a directory containing one, a raw V8 coverage directory (`NODE_V8_COVERAGE`), or a single V8 covera… |
| coverage_gaps | boolean|null | – | Explicitly request static test coverage gaps: runtime files and exports with no test dependency path. A provided config file may also enable coverage gaps via `rules.coverage-gaps` when no health sec… |
| coverage_root | string|null | – | Absolute prefix to strip from coverage data paths before prepending the project root. Use when coverage was generated in a different environment (CI runner, Docker). When omitted, `FALLOW_COVERAGE_RO… |
| css | boolean|null | – | Add a structural CSS analytics section (`css_analytics`): specificity hotspots, `!important` density, over-complex selectors, deep nesting, design-token sprawl (distinct colors / font-sizes / z-index… |
| effort | string|null | – | Analysis effort level. Controls the depth of analysis: "low" (fast, surface-level), "medium" (balanced, default), "high" (thorough, includes all heuristics). |
| file_scores | boolean|null | – | Show only per-file health scores, sorted by risk-aware triage concern: lower maintainability index and higher CRAP risk first. |
| group | string|null | – | Keep only the matching groups of a `group_by` run: exact group keys, globs, and `!`-prefixed negations, comma-separated. Project-level sections are not filtered. Requires `group_by`. Passed through t… |
| group_by | string|null | – | Group health findings by CODEOWNERS ownership, directory, workspace package, or GitLab CODEOWNERS section. Values: "owner", "directory", "package", "section". `section` attaches an `owners: string[]`… |
| hotspots | boolean|null | – | Show only hotspots: files that are both complex and frequently changing. |
| low_traffic_threshold | number|null | – | Fraction of `trace_count` below which an invoked function is classified `low_traffic` rather than `active`. Expressed as a decimal (0.001 = 0.1%). Inherits the sidecar default (0.001) when omitted. T… |
| max_cognitive | integer|null | – | Maximum cognitive complexity threshold. Functions exceeding this are reported. |
| max_crap | number|null | – | Maximum CRAP score threshold (default 30.0). Functions meeting or exceeding this score are reported alongside complexity findings. Pair with `coverage` for accurate per-function CRAP; without Istanbu… |
| max_cyclomatic | integer|null | – | Maximum cyclomatic complexity threshold. Functions exceeding this are reported. |
| max_file_lines | integer|null | – | Maximum physical lines per file (default 0, off). A longer file is reported as a complexity finding with `exceeded: "file_lines"`. Passed through to the CLI's `--max-file-lines` flag. |
| min_commits | integer|null | – | Minimum commits for a file to appear in hotspot ranking. |
| min_invocations_hot | integer|null | – | Minimum invocation count for a function to be classified as a hot path in runtime-coverage output. Inherits the CLI default (100) when omitted. Takes effect only when `runtime_coverage` is also set;… |
| min_observation_volume | integer|null | – | Minimum total trace volume before the sidecar may emit high-confidence `safe_to_delete` or `review_required` verdicts. Below this threshold, confidence is capped at `medium` to protect against overco… |
| min_score | number|null | – | Fail if the health score is below this threshold (0–100). Implies --score. |
| min_severity | string|null | – | Only exit with error for findings at or above this severity (moderate, high, critical). |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| ownership | boolean|null | – | Attach ownership signals (bus factor, contributors, declared owner, drift) to hotspot entries. Implies `hotspots`. Requires git. |
| ownership_email_mode | – | – | Privacy mode for author emails when `ownership` is enabled. Implies `ownership`. Defaults to `handle` server-side when omitted. |
| production | boolean|null | – | Only analyze production code (excludes tests, stories, dev files). |
| root | string|null | – | Project root; defaults to the working directory. |
| runtime_coverage | string|null | – | Path to runtime coverage input. Accepts a V8 coverage directory (`NODE_V8_COVERAGE=...`), a single V8 coverage JSON file, or an Istanbul `coverage-final.json`. A single local capture is free and runs… |
| save_baseline | string|null | – | Save current results as a baseline file for future comparisons. The path must resolve inside the project root, its Git work tree, the CI workspace or a temp directory. A relative path resolves agains… |
| save_snapshot | string|null | – | Save a vital signs snapshot. Provide a file path, or omit value for default (`.fallow/snapshots/{timestamp}.json`). The path must resolve inside the project root, its Git work tree, the CI workspace… |
| score | boolean|null | – | Show only the project health score (0–100) with letter grade (A/B/C/D/F). Runs duplication analysis automatically; pair with `hotspots=true` (or `targets=true`) for the churn-backed hotspot penalty. |
| since | string|null | – | Git history window for hotspot analysis. Accepts durations (6m, 90d, 1y) or ISO dates. It also sets the window for change coupling and change dispersion. When absent, hotspots read 6 months and chang… |
| sort | string|null | – | Sort order for results (e.g., "cyclomatic", "cognitive", "lines", "severity"). |
| summary | boolean|null | – | Include a natural-language summary of findings alongside the structured JSON output. |
| targets | boolean|null | – | Show only refactoring targets: ranked recommendations based on complexity, coupling, churn, and dead code. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| top | integer|null | – | Number of top results to return. |
| trend | boolean|null | – | Compare current metrics against the most recent saved snapshot and show per-metric deltas. Implies --score. Reads from `.fallow/snapshots/`. |
| trend_from | string|null | – | Compare current metrics against this snapshot file instead of the newest file in `.fallow/snapshots/`. Implies `trend`. With `group_by`, each group is compared by key when the snapshot holds the same… |
| type_aware | boolean|null | – | Enable the TypeScript semantic backend. `false` keeps the run syntactic, also when the config turns type-aware analysis on. `type_aware_projects` or `type_aware_require` turns it on and wins over `fa… |
| type_aware_projects | array|null | – | Explicit tsconfig paths for type-aware analysis. |
| type_aware_require | – | – | Whether incomplete semantic evidence is advisory or gating. |
| type_coupling | boolean|null | – | Include advisory project-local public-signature type coupling. |
| workspace | string|null | – | Workspace packages to analyze: name or repo-relative path, comma-separated list, globs, `!` negation. |
No output schema declared.
No examples provided.
check_runtime_coverage ~1,144
Merge runtime-coverage data into the health report. Focused entry point for the runtime-coverage pipeline: pass a V8 coverage directory (`NODE_V8_COVERAGE=<dir>`), a single V8 coverage JSON file, or an Istanbul `coverage-final.json` via the required `coverage` field. A single local capture is free and runs without a license; continuous or multi-capture runtime monitoring (multiple JSON files in a V8 directory) requires an active license JWT (start a 30-day trial with `fallow license activate --trial --email <addr>`; check state with `fallow license status`). Returns structured JSON with a `runtime_coverage` block containing surfaced `findings` verdicts (`safe_to_delete` / `review_required` / `low_traffic` / `coverage_unavailable`), stable content-hash IDs (`fallow:prod:<hash>`), evidence, percentile-ranked hot paths (each with `start_line` and `end_line` so consumers can match against a PR diff), and on protocol-0.3+ sidecars a `summary.capture_quality` block that flags short-window captures. The sidecar may still classify other functions as `active`, but the CLI omits those from `runtime_coverage.findings` to keep the surfaced list actionable. Tunable via `min_invocations_hot` (hot-path threshold, default 100), `min_observation_volume` (high-confidence verdict floor, default 5000), and `low_traffic_threshold` (active/low_traffic split, default 0.001). `group_by` partitions results by CODEOWNERS / directory / package / section. PR-context behavior: when `FALLOW_DIFF_FILE` (path to a unified diff) is set in the agent's process environment, the top-level `runtime_coverage.verdict` promotes `hot-path-touched` over `cold-code-detected` so reviewers see the diff-tied signal first, AND every hot path is narrowed to functions whose `[start_line, end_line]` overlaps an added hunk. `FALLOW_CHANGED_SINCE` (git ref) also scopes (file-level). Without a change scope the verdict stays cold-code-primary and all hot paths are returned. The full unprioritized list is always in `run…
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| config | string|null | – | Path to a fallow config file. |
| coverage | string | yes | Path to runtime coverage input. Accepts a V8 coverage directory (`NODE_V8_COVERAGE=<dir>`), a single V8 coverage JSON file, or an Istanbul `coverage-final.json`. Required. |
| group_by | string|null | – | Group health findings by CODEOWNERS ownership, directory, workspace package, or GitLab CODEOWNERS section. Values: "owner", "directory", "package", "section". `section` attaches an `owners: string[]`… |
| low_traffic_threshold | number|null | – | Fraction of `trace_count` below which an invoked function is classified `low_traffic` rather than `active`. Expressed as a decimal (0.001 = 0.1%). Inherits the sidecar default (0.001) when omitted. |
| max_crap | number|null | – | Maximum CRAP score threshold (default 30.0). Functions meeting or exceeding this score appear as findings alongside complexity violations. Production V8 coverage yields the most accurate per-function… |
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| min_invocations_hot | integer|null | – | Minimum invocation count for a function to be classified as a hot path. Inherits the CLI default (100) when omitted. |
| min_observation_volume | integer|null | – | Minimum total trace volume before the sidecar may emit high-confidence `safe_to_delete` or `review_required` verdicts. Below this threshold, confidence is capped at `medium` to protect against overco… |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| production | boolean|null | – | Only analyze production code (excludes tests, stories, dev files). |
| root | string|null | – | Project root; defaults to the working directory. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| top | integer|null | – | Show only the top N runtime findings, hot paths, file scores, and refactoring targets. Passed through to the CLI's `--top` flag. |
| workspace | string|null | – | Workspace packages to analyze: name or repo-relative path, comma-separated list, globs, `!` negation. |
No output schema declared.
No examples provided.
code_execute ~1,132
Execute a bounded, read-only JavaScript Code Mode snippet against fallow's MCP host API. `code` must be a JavaScript function expression or function body that receives `{ fallow, root }` and returns a JSON-serializable value. The embedded sandbox exposes only a typed `fallow` object with read-only analysis calls: analyze, combined, checkChanged, checkArchitecture, securityCandidates, findDupes, projectInfo, traceExport, traceFile, impactClosure, traceDependency, traceClone, checkHealth, audit, explain, listBoundaries, featureFlags, impact, checkRuntimeCoverage, getHotPaths, getBlastRadius, getImportance, getCleanupCandidates, plus `fallow.run(tool, params)` for the same allowlist. Similar-code (15-minute timeouts) and mutation are excluded; use the standalone find_similar_code, inspect_similar_code, mutation_plan, and mutation_inspect MCP tools. Mutating fix tools are intentionally not exposed. The sandbox has no filesystem, network, module imports, process, require, Deno, Bun, or shell access, and no dynamic code compilation: eval, Function, and the async and generator function constructors are removed, including the `constructor` route reachable through function prototypes. `root` is injected into host calls that omit params.root. `timeout_ms` caps JS execution and subprocess-backed host calls. In Code Mode, analyze, checkArchitecture, securityCandidates, findDupes, impactClosure, checkHealth, audit, impact, checkRuntimeCoverage, getHotPaths, getBlastRadius, getImportance, and getCleanupCandidates stay subprocess-backed and are killed on timeout. Every other host call runs in this process, where `timeout_ms` both answers you on time and sets that call's cancellation token: the analysis is asked to stop rather than only abandoned. The stop is cooperative and has no upper bound, because a token set inside a long analysis stage is not read until that stage ends, so the work may still be winding down after the call returns, and while it is the next in-process call fa…
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | JavaScript function expression or function body. The function receives `{ fallow, root }` and must return a JSON-serializable value. |
| max_output_bytes | integer|null | – | Maximum total bytes of fallow JSON output that sandbox host calls may read. Defaults to 1000000 and is capped at 4000000. |
| root | string|null | – | Default project root injected into fallow host calls when their params omit `root`. |
| timeout_ms | integer|null | – | Overall sandbox timeout in milliseconds. Defaults to 5000 and is capped at 30000. |
No output schema declared.
No examples provided.
decision_surface ~668
Surface the consequential structural decisions a change embeds, each framed as a judgment question for a human with taste (`fallow decision-surface --format json`). The apex of the review brief and the single call that puts taste-decisions in front of a reviewer; separable and cheap, it runs the same changed-code analysis as the brief, not the full project pipeline. Returns `kind: "decision-surface"` with `schema_version`, a ranked `decisions[]` list, an optional `truncated` note, and `signal_count`. Each decision carries a `signal_id` (a deterministic anchor to the fallow-emitted candidate it frames; an agent decision whose `signal_id` fallow did not emit must be rejected, so a decision cannot name a signal that fallow did not find), a `category` (exactly one of `coupling-boundary`, `public-api-contract` and `dependency`), the framed `question`, the `anchor_file`/`anchor_line`, the `blast` (modules affected beyond the diff) and `consequence` rank, the routed `expert[]` (who to ask) with a `bus_factor_one` flag, and structured `actions[]` (`ask-expert`, `suppress`). The surface is capped to a small number of decisions (default 4, configurable via `max_decisions`, clamped to 3-5); decisions beyond the cap collapse into `truncated`. Every `coupling-boundary` and `public-api-contract` decision is suppressible with a `// fallow-ignore` comment on the anchor file (the `suppress` action carries the paste-ready comment); a `dependency` decision anchors on a `package.json`, which cannot carry a comment, so it has no `suppress` action. Always exits 0 (advisory, never a gate). Use `base` to pick the comparison point (defaults to the git merge-base). Use this to answer "what are the few decisions in this change that actually need human judgment?" rather than scanning the whole diff.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| base | string|null | – | Git ref to compare against (e.g., "main", "HEAD~5"). When unset, the base is the git merge-base against the branch's upstream or the remote default (`origin/main`); set `FALLOW_AUDIT_BASE` in the ser… |
| config | string|null | – | Path to a fallow config file. |
| max_decisions | integer|null | – | Cap on the number of consequential structural decisions surfaced (the working-memory limit). Default 4; clamped to the 3-5 band (4 plus or minus 1). |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| root | string|null | – | Project root; defaults to the working directory. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| workspace | string|null | – | Workspace packages to analyze: name or repo-relative path, comma-separated list, globs, `!` negation. |
No output schema declared.
No examples provided.
fallow_explain ~129
Explain one fallow issue type without running analysis. Returns the rule id, name, rationale, worked example, fix guidance, and docs URL as JSON. Use this before applying fixes when an agent or reviewer needs to understand what a finding means. If your client exposes MCP resources, `fallow://explain/{issue_type}` serves the same document as a cacheable resource read.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_type | string | yes | Issue type or rule id to explain, for example "unused-export", "fallow/unused-dependency", "high-complexity", or "code-duplication". |
No output schema declared.
No examples provided.
feature_flags ~325
Detect feature flag patterns in a TypeScript/JavaScript project. Identifies environment variable flags (process.env.FEATURE_*), SDK calls from common providers, and config object patterns. Returns flag locations, detection confidence, and cross-reference with dead code findings. `retirement: true` adds advisory retirement rows (reasons, git age, evidence).
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| config | string|null | – | Path to a fallow config file. |
| flag_age | string|null | – | Flag age: "blame" (default, lower bound), "pickaxe" or "off". Needs `retirement`. |
| flag_state | string|null | – | Offline vendor flag export for the vendor reasons; relative to `root`. Needs `retirement`. |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| production | boolean|null | – | Only analyze production code (excludes tests, stories, dev files). |
| retirement | boolean|null | – | Add the `retirement` block: one row per flag with reasons, git age and evidence. |
| root | string|null | – | Project root; defaults to the working directory. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| top | integer|null | – | Show only the top N flags. |
| workspace | string|null | – | Workspace packages to analyze: name or repo-relative path, comma-separated list, globs, `!` negation. |
No output schema declared.
No examples provided.
find_dupes ~1,345
Find code duplication across the project. Detects clone groups (identical or similar code blocks) with configurable detection modes and thresholds. Returns clone families with refactoring suggestions. On a Rust root, it runs `cargo fallow dupes` (mode, min_tokens, min_lines, threshold). Each clone_groups[] entry carries a stable `fingerprint` (dup:<id>); pass it to the trace_clone tool to deep-dive that group (locations, an extract-function suggestion with estimated savings, and a best-effort suggested name). Set top=N to show only the N highest-ranked clone groups. Ranking combines token count, occurrence count, and a capped spread boost for distant files or same-file locations. Set group_by to "owner" (CODEOWNERS), "directory", "package" (workspace), or "section" (GitLab CODEOWNERS `[Section]` headers, with `owners` metadata per group) to partition results. Import declarations are excluded from clone detection by default (sorted import blocks are a formatting artifact, not copy-paste); pass ignore_imports=false to count them again. Clone instances omit their verbatim `fragment` text over MCP (it was most of the payload, and `file` plus the line/column range addresses the same code); set include_fragments=true to get it back. explain_skipped only changes the human-format skipped-default-ignores note (human/markdown CLI output); MCP JSON responses stay clean. Supports config, workspace scoping, baseline comparisons, and performance tuning (no_cache, threads).
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| baseline | string|null | – | Compare results against a saved baseline file. Only new clone groups (not in the baseline) are reported. The response carries `baseline_staleness`: read `gate_trips` to see whether the baseline has e… |
| changed_since | string|null | – | Git ref to compare against when limiting duplication to changed files. |
| config | string|null | – | Path to a fallow config file. |
| cross_language | boolean|null | – | Enable cross-language detection (strips TypeScript type annotations for TS/JS matching). |
| explain_skipped | boolean|null | – | Show a per-pattern breakdown for default duplicate ignores. `dupes` prints only that breakdown; the built-in discovery ignores are reported by `check`, `dead-code`, `audit` and the default run. Human… |
| group_by | string|null | – | Group findings by CODEOWNERS ownership, directory, workspace package, or GitLab CODEOWNERS section. Values: "owner", "directory", "package", "section". |
| ignore_imports | boolean|null | – | Exclude import declarations from clone detection. Defaults to `true` (sorted import blocks are a formatting artifact, not copy-paste); set `false` to count them again. |
| ignore_symlinks | boolean|null | – | Omit clone instances whose path is a symlink or lies under a symlinked directory. Defaults to the project config; set `false` to report them even when the config sets `ignoreSymlinks`. |
| include_fragments | boolean|null | – | Include the verbatim source text on each clone instance. Defaults to false: `file` plus the line and column range address the same code, and the text is most of the response. Set true only when you n… |
| min_lines | integer|null | – | Minimum line count for a clone. Defaults to the project config, or 5 if unset. |
| min_occurrences | integer|null | – | Minimum number of occurrences before a clone group is reported. Raise to focus on widespread copy-paste and skip pair-only clones. Defaults to the project config, or 2 if unset. |
| min_tokens | integer|null | – | Minimum token count for a clone. Defaults to the project config, or 50 if unset. |
| mode | string|null | – | Detection mode: "strict", "mild", "weak", or "semantic". Defaults to the project config, or "mild" if unset. |
| near | boolean|null | – | Detect function-scoped near-miss clones in addition to exact clones. |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| no_package_baselines | boolean|null | – | Ignore the per-package refs of `workspaces.changedSince` for this call, so every workspace package is analyzed in full scope. Use it to judge or save a whole-project baseline. |
| root | string|null | – | Project root; defaults to the working directory. |
| save_baseline | string|null | – | Save current results as a baseline file for future comparisons. The path must resolve inside the project root, its Git work tree, the CI workspace or a temp directory. A relative path resolves agains… |
| skip_local | boolean|null | – | Only report cross-directory duplicates. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| threshold | number|null | – | Fail if duplication exceeds this percentage (0 = no limit). Defaults to the project config, or 0 if unset. |
| top | integer|null | – | Show only the N highest-ranked clone groups. `clone_families[]` is rebuilt from the groups that survive, so it narrows too. `stats` keeps describing the whole corpus; read `clone_groups_shown` / `clo… |
| workspace | string|null | – | Workspace packages to analyze: name or repo-relative path, comma-separated list, globs, `!` negation. |
No output schema declared.
No examples provided.
find_similar_code ~478
Find semantically similar functions with Fallow's exact pinned local model. Results are unverified candidates, not probabilities, duplication findings, refactor instructions, or CI gates. Source stays on the local machine. Each candidate carries stable candidate_id and review_key identities, exact locations, reproducible provider/model provenance, completion accounting, and read-only inspect/review actions. The command never downloads a model: if explicit setup has not happened, it returns structured guidance to run `fallow similar-code setup --local`. Use threshold only as a candidate-retrieval cutoff, then call inspect_similar_code before deciding whether two functions are behaviorally equivalent or safe to consolidate. Supports root, config, workspace, changed_since, changed_workspaces, paths, threshold, min_lines, top, no_cache, and threads. Cold local inference has a dedicated 15-minute subprocess window; FALLOW_TIMEOUT_SECS still overrides it when an operator needs a different bound.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| changed_since | string|null | – | Git ref used to report candidate pairs touching changed files. |
| changed_workspaces | string|null | – | Scope candidate reporting to workspaces touched since this git ref. |
| config | string|null | – | Path to a fallow config file. |
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| min_lines | integer|null | – | Minimum extracted source lines per function. |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| paths | array|null | – | Report candidate pairs touching one of these project-relative files. |
| root | string|null | – | Project root; defaults to the working directory. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| threshold | number|null | – | Minimum cosine similarity from zero through one. This is not a probability or verification verdict. |
| top | integer|null | – | Cap returned candidates after bounded full-corpus comparison. |
| workspace | string|null | – | Workspace packages to scope candidates to; mutually exclusive with `changed_workspaces`. |
No output schema declared.
No examples provided.
fix_apply ~1,270
Apply auto-fixes to the project. Removes unused exports from the public API, may delete dead exported enum declarations, deletes unused dependencies from package.json, removes unused enum members, removes unused pnpm catalog entries (rewriting empty groups to `{}` so pnpm install does not reject null), and appends duplicate-export `ignoreExports` rules to the fallow config file. When no fallow config exists outside a monorepo subpackage, this CREATES `.fallowrc.json` using `fallow init`'s framework-aware scaffolding (`$schema`, `entry`, `ignorePatterns`, framework defaults) and layers the `ignoreExports` rules on top. Inside a monorepo subpackage (workspace marker `pnpm-workspace.yaml` / `package.json#workspaces` / `turbo.json` / `lerna.json` / `rush.json` above the invocation directory) the create-fallback refuses and emits `skip_reason: "monorepo_subpackage"` with a relative `workspace_root` path; the agent should re-run `fallow init` at the workspace root or invoke from there. Set `no_create_config: true` to opt out of the create-fallback entirely (recommended for CI and unattended use); the duplicate-export path is skipped with `skip_reason: "no_create_config"` and source-file edits proceed normally. When a source file's xxh3 content hash at fix time differs from the hash captured during the in-process analysis (parallel editor save, CI rebase, or other tool mutated the file between analysis and write), the per-file fix is skipped with `skip_reason: "content_changed"`; the envelope's top-level `skipped_content_changed` count is incremented and the run exits with code 2 so CI surfaces the mismatch instead of treating the partial run as a clean no-op. When a source file mixes CRLF and bare-LF line endings, the per-file fix is skipped with `skip_reason: "mixed_line_endings"`; the envelope's top-level `skipped_mixed_line_endings` count is incremented and the run exits with code 2. This skip is NOT self-healing: re-running fallow alone does not normalize the file an…
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| config | string|null | – | Path to a fallow config file. |
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| no_create_config | boolean|null | – | Refuse to create a new fallow config file when none exists. Use this from pre-commit hooks and CI bots where silently materializing a new top-level config file would surprise the user. |
| production | boolean|null | – | Production mode: exclude test, story, and dev files, only start/build scripts, and report type-only dependencies. |
| root | string|null | – | Project root; defaults to the working directory. |
| show_cascade | boolean|null | – | Also fix the unused exports, types, class members and enum members of unused files. By default `fix` skips them, as the report hides them. Passed through to the CLI's `--show-cascade` flag. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| workspace | string|null | – | Workspace packages to analyze: name or repo-relative path, comma-separated list, globs, `!` negation. |
No output schema declared.
No examples provided.
fix_preview ~927
Preview auto-fixes without modifying any files. Shows what would be changed: which unused exports would be removed, which unused dependencies would be deleted from package.json, which unused enum members would be removed, which unused pnpm catalog entries would be cleaned up, and which duplicate-export `ignoreExports` rules would be added to the fallow config file. For `add-to-config` actions, each fix entry carries a `proposed_diff` field with the unified-diff preview of the proposed config write. When no fallow config exists outside a monorepo subpackage, fix_apply would CREATE `.fallowrc.json` using `fallow init`'s framework-aware scaffolding (`$schema`, `entry`, `ignorePatterns`, etc.) and layer the `ignoreExports` rules on top; preview entries on that path carry `created_files: [".fallowrc.json"]`. Set `no_create_config: true` to skip the config-creation path with `skip_reason: "no_create_config"`; source-file previews are unaffected. When a source file's xxh3 content hash at preview time differs from the hash captured during the in-process analysis (a concurrent source edit), the per-file entry is emitted with `skip_reason: "content_changed"` and the envelope's top-level `skipped_content_changed` count is incremented; re-run after refreshing analysis. When a source file mixes CRLF and bare-LF line endings, the per-file entry is emitted with `skip_reason: "mixed_line_endings"` and the envelope's top-level `skipped_mixed_line_endings` count is incremented; this skip is NOT self-healing because re-running fallow alone does not normalize the file. The agent must run `dos2unix <path>` (or instruct the user to set `git config core.autocrlf input` and re-checkout) before re-running. When an unused export lives in a test, mock, or fixture directory, or in a file that itself has an unresolved import, its removal is withheld as low confidence because the consumer may be invisible to static analysis: the per-file entry carries `skip_reason: "low_confidence_off_graph"` o…
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| config | string|null | – | Path to a fallow config file. |
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| no_create_config | boolean|null | – | Refuse to create a new fallow config file when none exists. Use this from pre-commit hooks and CI bots where silently materializing a new top-level config file would surprise the user. |
| production | boolean|null | – | Production mode: exclude test, story, and dev files, only start/build scripts, and report type-only dependencies. |
| root | string|null | – | Project root; defaults to the working directory. |
| show_cascade | boolean|null | – | Also fix the unused exports, types, class members and enum members of unused files. By default `fix` skips them, as the report hides them. Passed through to the CLI's `--show-cascade` flag. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| workspace | string|null | – | Workspace packages to analyze: name or repo-relative path, comma-separated list, globs, `!` negation. |
No output schema declared.
No examples provided.
get_blast_radius ~782
Return first-class blast-radius context alongside local runtime coverage. Pass `coverage` as a V8 coverage directory, single V8 JSON file, or Istanbul `coverage-final.json`. A single local capture is free and runs without a license; continuous or multi-capture runtime monitoring requires an active license. Returns the standard health JSON; agents should read `runtime_coverage.blast_radius`, which contains stable `fallow:blast:<hash>` IDs, caller counts, traffic-weighted caller reach, and low/medium/high risk bands. This blast-radius signal augments context only: it scores the RISK of changing a function. It MUST NOT gate `safe_to_delete` or a confidence score (a function having callers does not make it 'keep'); only the three-state runtime tracking signal (called / never_called / untracked) can issue a deletion verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| config | string|null | – | Path to a fallow config file. |
| coverage | string | yes | Path to runtime coverage input. Accepts a V8 coverage directory (`NODE_V8_COVERAGE=<dir>`), a single V8 coverage JSON file, or an Istanbul `coverage-final.json`. Required. |
| group_by | string|null | – | Group health findings by CODEOWNERS ownership, directory, workspace package, or GitLab CODEOWNERS section. Values: "owner", "directory", "package", "section". `section` attaches an `owners: string[]`… |
| low_traffic_threshold | number|null | – | Fraction of `trace_count` below which an invoked function is classified `low_traffic` rather than `active`. Expressed as a decimal (0.001 = 0.1%). Inherits the sidecar default (0.001) when omitted. |
| max_crap | number|null | – | Maximum CRAP score threshold (default 30.0). Functions meeting or exceeding this score appear as findings alongside complexity violations. Production V8 coverage yields the most accurate per-function… |
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| min_invocations_hot | integer|null | – | Minimum invocation count for a function to be classified as a hot path. Inherits the CLI default (100) when omitted. |
| min_observation_volume | integer|null | – | Minimum total trace volume before the sidecar may emit high-confidence `safe_to_delete` or `review_required` verdicts. Below this threshold, confidence is capped at `medium` to protect against overco… |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| production | boolean|null | – | Only analyze production code (excludes tests, stories, dev files). |
| root | string|null | – | Project root; defaults to the working directory. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| top | integer|null | – | Show only the top N runtime findings, hot paths, file scores, and refactoring targets. Passed through to the CLI's `--top` flag. |
| workspace | string|null | – | Workspace packages to analyze: name or repo-relative path, comma-separated list, globs, `!` negation. |
No output schema declared.
No examples provided.
get_cleanup_candidates ~706
Return cleanup candidates grounded in local runtime coverage. Pass `coverage` as a V8 coverage directory, single V8 JSON file, or Istanbul `coverage-final.json`. A single local capture is free and runs without a license; continuous or multi-capture runtime monitoring requires an active license. Returns the standard health JSON; agents should read `runtime_coverage.findings` for `safe_to_delete`, `review_required`, `low_traffic`, and `coverage_unavailable` verdicts.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| config | string|null | – | Path to a fallow config file. |
| coverage | string | yes | Path to runtime coverage input. Accepts a V8 coverage directory (`NODE_V8_COVERAGE=<dir>`), a single V8 coverage JSON file, or an Istanbul `coverage-final.json`. Required. |
| group_by | string|null | – | Group health findings by CODEOWNERS ownership, directory, workspace package, or GitLab CODEOWNERS section. Values: "owner", "directory", "package", "section". `section` attaches an `owners: string[]`… |
| low_traffic_threshold | number|null | – | Fraction of `trace_count` below which an invoked function is classified `low_traffic` rather than `active`. Expressed as a decimal (0.001 = 0.1%). Inherits the sidecar default (0.001) when omitted. |
| max_crap | number|null | – | Maximum CRAP score threshold (default 30.0). Functions meeting or exceeding this score appear as findings alongside complexity violations. Production V8 coverage yields the most accurate per-function… |
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| min_invocations_hot | integer|null | – | Minimum invocation count for a function to be classified as a hot path. Inherits the CLI default (100) when omitted. |
| min_observation_volume | integer|null | – | Minimum total trace volume before the sidecar may emit high-confidence `safe_to_delete` or `review_required` verdicts. Below this threshold, confidence is capped at `medium` to protect against overco… |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| production | boolean|null | – | Only analyze production code (excludes tests, stories, dev files). |
| root | string|null | – | Project root; defaults to the working directory. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| top | integer|null | – | Show only the top N runtime findings, hot paths, file scores, and refactoring targets. Passed through to the CLI's `--top` flag. |
| workspace | string|null | – | Workspace packages to analyze: name or repo-relative path, comma-separated list, globs, `!` negation. |
No output schema declared.
No examples provided.
get_cloud_deployment_changes ~293
Read how production behavior changed between two deployments from Fallow Cloud. Backed by `fallow coverage deployment-changes --format json`. `repo` is required; `sha` defaults to `HEAD` of `root`, `base` to the previous deployment with production runtime. Each function has a change kind (`new_called`, `new_not_called`, `heated_up`, `cooled_down`, `stopped`, `unchanged`); `change`, `limit` and `cursor` filter and page. Read `comparable` first. Context only, never a deletion verdict. Needs `FALLOW_API_KEY` in the server environment.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string|null | – | Base deployment commit SHA. |
| change | string|null | – | One change kind to keep. |
| cursor | string|null | – | `meta.cursor` of the previous page. |
| limit | integer|null | – | Page size, 1 to 200. |
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| repo | string | yes | Repository as `owner/repo`. Required. |
| root | string|null | – | Project root; defaults to the working directory. |
| sha | string|null | – | Deployment commit SHA; defaults to `HEAD`. |
No output schema declared.
No examples provided.
get_cloud_review_packet ~330
Read production facts for a few changed files or functions from Fallow Cloud, with no full pull and no local analysis. Backed by `fallow coverage review-packet --format json`. `repo` is required; pass `files` and/or `functions` (`{file, name, line?}`), or neither to send the files changed against `base`. Rows carry `repo_path`, `tracking_state` (current deployment) and `period_tracking_state` (whole period); `evidence_window` is the real evidence span. A current `never_called` with `period_tracking_state: called` is not dead code. Needs `FALLOW_API_KEY` in the server environment; see `fallow://tools/get_cloud_review_packet`.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string|null | – | Base ref for the changed-file default. |
| commit_sha | string|null | – | Deployment commit SHA. |
| files | array|null | – | Repo-relative files, at most 1000. |
| functions | array|null | – | Functions, at most 1000. |
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| period_days | integer|null | – | Window in days, 1 to 90. |
| project_id | string|null | – | Project disambiguator. |
| repo | string | yes | Repository as `owner/repo`. Required. |
| root | string|null | – | Project root; defaults to the working directory. |
No output schema declared.
No examples provided.
get_cloud_runtime_context ~746
Pull runtime coverage for a repository from Fallow Cloud instead of a local V8 or Istanbul dump, and return the same `runtime_coverage` block the local runtime-coverage tools return. Backed by `fallow coverage analyze --cloud --format json`: Fallow Cloud is asked for the repository's runtime facts over the requested window, and the answer is joined against this project's static analysis, so `root` must be a checkout of the same repository. It makes a network call and needs a Fallow Cloud account (for a scoped question, get_cloud_review_packet is smaller); cloud pull is a Team-tier feature, and a repository your org cannot see is refused by the cloud rather than returned empty. The API key is never a parameter: the CLI reads `FALLOW_API_KEY` in the server's own environment, else the key that `fallow cloud login` stored. A call without a key stops before the analysis, with `isError`, `exit_code: 2`, and `code: "cloud_api_key_missing"`. `repo` (`owner/repo`) is required. `project_id`, `period_days` (1-90, default 30), `environment`, and `commit_sha` narrow what the cloud returns; `production`, `top`, and `min_invocations_hot` behave as they do on check_runtime_coverage. Read `runtime_coverage.findings` for `safe_to_delete` / `review_required` / `low_traffic` / `coverage_unavailable` verdicts, `runtime_coverage.hot_paths` for production hot paths, `runtime_coverage.blast_radius` and `runtime_coverage.importance` for review context that never gates a deletion verdict, `runtime_coverage.summary.data_source` to confirm the evidence is `cloud`, and `runtime_coverage.warnings` for the codes that explain a thin answer (`no_runtime_data`, `cloud_functions_unmatched`).
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| commit_sha | string|null | – | Commit SHA filter for the runtime facts the cloud returns. |
| config | string|null | – | Path to a fallow config file. |
| environment | string|null | – | Runtime environment filter, for example `production`. |
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| min_invocations_hot | integer|null | – | Minimum invocation count for a function to be classified as a hot path. Inherits the CLI default (100) when omitted. |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| period_days | integer|null | – | Runtime observation window in days, 1 to 90. Inherits the CLI default (30) when omitted. |
| production | boolean|null | – | Only analyze production code (excludes tests, stories, dev files). |
| project_id | string|null | – | Project disambiguator when one repository reports several projects. |
| repo | string | yes | Repository Fallow Cloud holds runtime facts for, as `owner/repo`. Required. |
| root | string|null | – | Project root; defaults to the working directory. It must be a checkout of `repo`: cloud functions are joined against its static analysis. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| top | integer|null | – | Show only the top N runtime findings and hot paths. |
No output schema declared.
No examples provided.
get_hot_paths ~995
Return production hot paths from a local V8 or Istanbul runtime coverage dump. Pass `coverage` as a V8 coverage directory, single V8 JSON file, or Istanbul `coverage-final.json`. A single local capture is free and runs without a license; continuous or multi-capture runtime monitoring requires an active license. Returns the standard health JSON; agents should read `runtime_coverage.hot_paths`, which is sorted by percentile and invocation count. Each entry carries `start_line` and `end_line` so agents can match the function's full body against a PR diff. Use `top` to cap the returned hot paths. Each hot path with a static counterpart also carries `optimization_target`: `cost_score` (invocations multiplied by the per-call cost), `cost_basis` (`inner_iterations` from V8 block counts, else `cognitive`), `cognitive`, `cyclomatic`, `line_count`, and `inner_iterations_per_call`. To pick speed work, sort by `cost_basis` (`inner_iterations` first), then by `cost_score` descending: scores on different bases do not compare. The hot paths are selected and capped by invocations, so a function with fewer calls but more work per call can be absent. Use `get_importance` to judge the risk of a change. Environment-driven scoping: if `FALLOW_DIFF_FILE` (path to a unified diff) is set in the agent's process env, hot paths are narrowed to functions whose `[start_line, end_line]` overlaps an added hunk; a file the diff touched but with no added lines (deletion-only / pure-rename) drops its hot paths rather than falling through to changed-since file-level matching. `FALLOW_CHANGED_SINCE` (git ref) covers the fallback case (file-level match for files NOT in the diff at all). Unset both for project-wide hot paths.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| config | string|null | – | Path to a fallow config file. |
| coverage | string | yes | Path to runtime coverage input. Accepts a V8 coverage directory (`NODE_V8_COVERAGE=<dir>`), a single V8 coverage JSON file, or an Istanbul `coverage-final.json`. Required. |
| group_by | string|null | – | Group health findings by CODEOWNERS ownership, directory, workspace package, or GitLab CODEOWNERS section. Values: "owner", "directory", "package", "section". `section` attaches an `owners: string[]`… |
| low_traffic_threshold | number|null | – | Fraction of `trace_count` below which an invoked function is classified `low_traffic` rather than `active`. Expressed as a decimal (0.001 = 0.1%). Inherits the sidecar default (0.001) when omitted. |
| max_crap | number|null | – | Maximum CRAP score threshold (default 30.0). Functions meeting or exceeding this score appear as findings alongside complexity violations. Production V8 coverage yields the most accurate per-function… |
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| min_invocations_hot | integer|null | – | Minimum invocation count for a function to be classified as a hot path. Inherits the CLI default (100) when omitted. |
| min_observation_volume | integer|null | – | Minimum total trace volume before the sidecar may emit high-confidence `safe_to_delete` or `review_required` verdicts. Below this threshold, confidence is capped at `medium` to protect against overco… |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| production | boolean|null | – | Only analyze production code (excludes tests, stories, dev files). |
| root | string|null | – | Project root; defaults to the working directory. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| top | integer|null | – | Show only the top N runtime findings, hot paths, file scores, and refactoring targets. Passed through to the CLI's `--top` flag. |
| workspace | string|null | – | Workspace packages to analyze: name or repo-relative path, comma-separated list, globs, `!` negation. |
No output schema declared.
No examples provided.
get_importance ~778
Return first-class production-importance context from local runtime coverage plus static health signals. Pass `coverage` as a V8 coverage directory, single V8 JSON file, or Istanbul `coverage-final.json`. A single local capture is free and runs without a license; continuous or multi-capture runtime monitoring requires an active license. Returns the standard health JSON; agents should read `runtime_coverage.importance`, which contains stable `fallow:importance:<hash>` IDs, invocations, cyclomatic complexity, owner count, a 0-100 score, and a templated reason. This importance signal augments context only. It MUST NOT gate `safe_to_delete` or a confidence score (a high or low score never decides deletion); only the three-state runtime tracking signal (called / never_called / untracked) can issue a deletion verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| config | string|null | – | Path to a fallow config file. |
| coverage | string | yes | Path to runtime coverage input. Accepts a V8 coverage directory (`NODE_V8_COVERAGE=<dir>`), a single V8 coverage JSON file, or an Istanbul `coverage-final.json`. Required. |
| group_by | string|null | – | Group health findings by CODEOWNERS ownership, directory, workspace package, or GitLab CODEOWNERS section. Values: "owner", "directory", "package", "section". `section` attaches an `owners: string[]`… |
| low_traffic_threshold | number|null | – | Fraction of `trace_count` below which an invoked function is classified `low_traffic` rather than `active`. Expressed as a decimal (0.001 = 0.1%). Inherits the sidecar default (0.001) when omitted. |
| max_crap | number|null | – | Maximum CRAP score threshold (default 30.0). Functions meeting or exceeding this score appear as findings alongside complexity violations. Production V8 coverage yields the most accurate per-function… |
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| min_invocations_hot | integer|null | – | Minimum invocation count for a function to be classified as a hot path. Inherits the CLI default (100) when omitted. |
| min_observation_volume | integer|null | – | Minimum total trace volume before the sidecar may emit high-confidence `safe_to_delete` or `review_required` verdicts. Below this threshold, confidence is capped at `medium` to protect against overco… |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| production | boolean|null | – | Only analyze production code (excludes tests, stories, dev files). |
| root | string|null | – | Project root; defaults to the working directory. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| top | integer|null | – | Show only the top N runtime findings, hot paths, file scores, and refactoring targets. Passed through to the CLI's `--top` flag. |
| workspace | string|null | – | Workspace packages to analyze: name or repo-relative path, comma-separated list, globs, `!` negation. |
No output schema declared.
No examples provided.
get_token_blast_radius ~504
Return design-token blast radius from static analysis. Runs `fallow health --css --format json`; agents should read `css_analytics.token_consumers`, a reverse index keyed by each token of its defining site plus a `consumer_count` and a capped located `consumers[]` sample of `{path,line,kind}`. Covers TWO token origins, disambiguated by token shape and consumer `kind`: Tailwind v4 `@theme` tokens (`token` is the `--`-prefixed custom property like `--color-brand`; `kind` in `theme-var` / `css-var` / `utility` / `apply`) AND CSS-in-JS token definitions (StyleX `defineVars` / `unstable_defineVarsNested`, vanilla-extract `createTheme` / `createThemeContract` / `createGlobalTheme`; `token` is the binding-qualified dotted access path like `vars.color.primary`, `namespace` is the defining binding, member reads use `js-member`, and StyleX theme-group calls use `js-call`). StyleX theme-group calls credit the complete resolved contract, including partial overrides and empty reset themes. The index is empty or absent on projects using neither. `consumer_count` is a static lower bound because computed class names, dynamic token structures, unresolved imports, and computed token access cannot always be counted. For Tailwind a `consumer_count` of 0 mirrors the unused-theme-token population (the dead-token verdict stays on `unused_theme_tokens` via check_health); CSS-in-JS tokens have no corroborating dead-token finding, so treat a CSS-in-JS 0 as weaker. Use this tool to scope the impact of editing or renaming a token, not to decide deletion.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| config | string|null | – | Path to a fallow config file. |
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| root | string|null | – | Project root; defaults to the working directory. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
No output schema declared.
No examples provided.
guard ~237
Report the architecture rules that apply to specific files before editing them: the file's boundary zone, which zones it may import from (same-zone imports are always allowed), forbidden call patterns, and every rule-pack policy in scope with its severity and suppression token. Works for files that do not exist yet, so it can be called before writing new code. A path that matches no configured zone returns an empty rule set rather than an error. It reads config only and runs no analysis; to find existing violations use `analyze` or `list_boundaries`.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| files | array | yes | Files to report on, project-root-relative. They do not need to exist yet. |
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| root | string|null | – | Project root; defaults to the working directory. |
No output schema declared.
No examples provided.
impact ~612
Read fallow's local value-tracking report. Runs NO analysis: it reads a per-project history file from the user's private config dir (never inside the repo), answering "what has fallow done for me over time" rather than "what is wrong now" (for live findings use analyze / audit / check_health). LOCAL-DEV ONLY: history accrues only on a developer's machine (local dev, or a persistent pre-commit gate); fallow never records in CI, so in CI / ephemeral runners this returns an empty report (enabled:false) and must NOT be used as a CI metric. Always returns a populated JSON object (never {}): branch on `enabled` and `enabled_source` (`project` = an explicit per-repo enable/disable, `user` = the user-global default, `default` = off). When `enabled:false`, use `explicit_decision` to decide what to say: `explicit_decision:false` means tracking was never set up here, so recommend the user run `fallow impact enable` (do not run it yourself); `explicit_decision:true` means the user deliberately disabled it here, so do NOT nag. Also branch on `record_count` (0 with enabled:true = set up but awaiting gate runs). When enabled with history it returns `surfacing` (issue counts from the most recent recorded run), `trend` (count delta vs the previous run; improving/declining/stable on the wire), `containment_count` + `recent_containment` (pre-commit gate runs that blocked a commit then later cleared), and a short-SHA `latest_git_sha` for correlation. On fallow with impact v1.5+ the report also carries `resolved_total` / `suppressed_total` / `recent_resolved` / `attribution_active`, crediting findings fallow saw genuinely fixed (code removed or refactored) and never counting a fallow-ignore suppression as a win; older fallow binaries omit these fields. On fallow with impact v1.6+ the report also carries `project_surfacing` / `project_trend`: a WHOLE-PROJECT view from the last full `fallow` run (additive optional under the same `schema_version`, omitted by older binaries). Treat changed…
| Name | Type | Req | Description |
|---|---|---|---|
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| root | string|null | – | Project root whose local value history to read (stored outside the repo); defaults to the working directory. |
No output schema declared.
No examples provided.
impact_all ~611
Roll EVERY tracked fallow project on this machine into one cross-repo value report (`fallow impact --all --format json`). Runs NO analysis: it reads the per-project history files in the user's private config dir, answering "what has fallow done for me across all my repos". Use this instead of `impact` when the agent wants a portfolio view rather than one repo; use `impact` (with `root`) for a single project. Returns `kind: "impact-cross-repo"` with `schema_version` "2", `project_count` (stores enumerated), `tracked_count` (projects with recorded history shown as rows), `unreadable_count` (corrupt/newer-schema stores skipped), a `totals` roll-up (resolved/contained/surfacing summed over ALL tracked projects, including repos since deleted from disk), and a `projects[]` array. Each project row carries a hashed `project_key` (never a filesystem path, and the only always-present identifier), an optional human `label` (the repo's directory basename; omitted on rows recorded by older fallow binaries, so fall back to `project_key` when `label` is null/absent), `last_recorded`, and a nested per-project `report`. Privacy: the aggregate exposes NO absolute paths, only the hash key plus the basename label. Projects that are enabled but have no recorded history yet are counted in `project_count` but excluded from `projects[]` rows. `sort` orders rows (`recent` default / `resolved` / `contained` / `name`); `limit` caps the rows returned while `totals` still reflect every tracked project. LOCAL-DEV ONLY: history accrues only on developer machines (fallow never records in CI), so in CI / ephemeral runners this returns zero tracked projects and must NOT be used as a CI metric. When `project_count` is 0, no project on this machine has tracking enabled yet: in a local dev session suggest the user run `fallow impact enable` in a repo they care about (do not run it yourself), but in CI stay silent because zero is the expected, non-actionable result. Read-only; the mutating enable / dis…
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer|null | – | Cap the number of project rows returned. Grand totals still reflect every tracked project, including any beyond the cap. Omit for all rows. |
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| sort | string|null | – | Row ordering: `recent` (default, most recently recorded project first), `resolved` (most findings resolved first), `contained` (most commits contained first), or `name` (alphabetical by project label… |
No output schema declared.
No examples provided.
impact_closure ~321
Trace a file's impact closure. Runs `fallow dead-code --impact-closure <path> --format json --quiet` and returns the transitive affected-but-not-in-diff set plus coordination gaps for file-contract consumers. Evidence for review planning, not proof that affected files are wrong. Gaps carry `search_visibility`; see fallow://tools/impact_closure. Supports root, config, production, workspace, no_cache, and threads.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| config | string|null | – | Path to a fallow config file. |
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| path | string | yes | Project-relative path to the file whose impact closure to trace. |
| production | boolean|null | – | Production mode: exclude test, story, and dev files, only start/build scripts, and report type-only dependencies. |
| root | string|null | – | Project root; defaults to the working directory. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| workspace | string|null | – | Workspace packages to analyze: name or repo-relative path, comma-separated list, globs, `!` negation. |
No output schema declared.
No examples provided.
inspect_similar_code ~410
Inspect one exact unverified candidate from find_similar_code without rerunning provider retrieval or global ranking. Pass candidate_id plus a bounded snapshot containing the unchanged discovery schema_version, generation, selected candidate, completion, and diagnostics fields. Current source is re-extracted and both source_sha256 values must still match before bounded source windows, syntactic behavior hints, graph relationships, reachability, callers/callees, ownership, churn, tests, and deterministic clone overlap are returned. Stale source fails closed. Missing evidence is represented explicitly, never inferred. This remains read-only and never declares behavioral equivalence or refactor safety.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| candidate_id | string | yes | Snapshot-stable candidate identity returned by `find_similar_code`. |
| config | string|null | – | Path to a fallow config file. |
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| root | string|null | – | Project root; defaults to the working directory. |
| snapshot | object | yes | Bounded exact-candidate snapshot object selected from the original discovery response. Pass generation, candidate, completion, and diagnostics unchanged; inspect validates current source hashes befor… |
No output schema declared.
No examples provided.
inspect_target ~1,080
Inspect one file or exported symbol and return one typed evidence bundle. Address a file with target={type:"file", file:"src/a.ts"}; address a symbol with target={type:"symbol", file:"src/a.ts", export_name:"foo"}. Composes existing read-only analysis systems only: trace_file, trace_export for symbols, file-scoped dead-code actions, duplication groups filtered to the file, complexity findings filtered to the file, security candidates scoped to the file, and the impact closure for the file (the transitive affected-but-not-in-diff set plus the coordination gap: modules that consume this file's contract but are not shown alongside it; a syntactic attention pointer, not a correctness proof). Set include_churn=true to attach target-level git churn from the in-process health hotspot subsystem; it is off by default, and missing git history is reported explicitly. Set cloud=true on a file target to attach the `cloud` evidence section of `fallow inspect --cloud` (Fallow Cloud production data per local function); repo selects the `owner/repo`. The key comes from the server environment or `fallow cloud login`, never from the call. The section status is ok, no_key, plan_required, unavailable, or untracked, and a status other than ok does not fail the call; see fallow://tools/inspect_target. Set format="compact" to get the plain text of `fallow inspect --format compact` (about 1 KB, no JSON) instead of the bundle. production is forwarded only to child analyses that support it: trace, dead-code, and health. Symbol targets include file-scoped evidence with explicit scope fields because file:line enclosing-symbol mapping is a follow-up. This bundled query runs independent evidence analyses in parallel; large repositories can exceed the default 120s subprocess timeout, so raise FALLOW_TIMEOUT_SECS when needed.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| cloud | boolean|null | – | Opt-in (default off): attach the Fallow Cloud `cloud` evidence section for a file target: production data per local function. The CLI reads the key: `FALLOW_API_KEY` in the server environment, else t… |
| config | string|null | – | Path to a fallow config file. |
| format | – | – | Response format: `json` (default) returns the evidence bundle. `compact` returns the plain text of `fallow inspect --format compact`: about 1 KB, one line per item, and no JSON. |
| include_churn | boolean|null | – | Opt-in (default off): attach target-level git churn evidence. Missing git history is returned as an explicit unavailable evidence section. |
| max_output_bytes | integer|null | – | Byte cap for this call's response. Lowers the server cap (default 1000000); over it the call is REFUSED (`isError`, `exit_code: 2`). |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| production | boolean|null | – | Production mode: exclude test, story, and dev files, only start/build scripts, and report type-only dependencies. Forwarded only to child analyses that support it: trace, dead-code, and health. |
| repo | string|null | – | Fallow Cloud repository for `cloud`, as `owner/repo`. Needs `cloud: true`. Precedence: this value, then `FALLOW_REPO` in the server environment, then the `origin` git remote. |
| root | string|null | – | Project root; defaults to the working directory. |
| symbol_chain | boolean|null | – | Opt-in (default off): also attach the best-effort symbol-level call chain (`fallow trace`) as the `symbol_chain` evidence section. Only meaningful for a symbol target. Best-effort and syntactic, and… |
| target | – | yes | The file or exported symbol to inspect. See the tool description for the two addressing shapes. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
| type_aware | boolean|null | – | Include project-wide TypeScript semantic evidence for symbol targets. `false` keeps the run syntactic, also when the config turns type-aware analysis on. `type_aware_projects` or `type_aware_require`… |
| type_aware_projects | array|null | – | Explicit tsconfig paths for type-aware analysis. |
| type_aware_require | – | – | Whether incomplete semantic evidence is advisory or gating. |
| workspace | string|null | – | Workspace packages to analyze: name or repo-relative path, comma-separated list, globs, `!` negation. |
No output schema declared.
No examples provided.
list_boundaries ~305
List architecture boundary zones and access rules configured for the project. Returns zone definitions (name, glob patterns, matched file count), access rules (which zones may import from which), and `logical_groups[]` (one entry per pre-expansion `autoDiscover` zone, surfacing the user-authored parent name, verbatim `auto_discover` paths, discovered `children`, `status` (`ok` / `empty` / `invalid_path`), `source_zone_index`, summed `file_count`, optional `authored_rule`, optional `fallback_zone` cross-reference for the Bulletproof case, optional `merged_from` when the parent name was declared multiple times, optional `original_zone_root` echo for monorepo subtree scopes, and optional `child_source_indices` attribution when multiple paths were authored). If boundaries are not configured, returns {"configured": false}; in that case, boundary violation checks will find no issues and can be skipped. Use this to understand the project's architecture constraints before running analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remote_extends | boolean|null | – | Allow trusted HTTPS config `extends` for this request. Defaults to false and never grants process-global trust. |
| config | string|null | – | Path to a fallow config file. |
| no_cache | boolean|null | – | Disable the incremental parse cache. |
| root | string|null | – | Project root; defaults to the working directory. |
| threads | integer|null | – | Parser thread count; defaults to CPU cores. |
No output schema declared.
No examples provided.
How do I install the Fallow MCP server?
Fallow runs locally as an npm package, launched with npx -y fallow mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · fallow
claude mcp add fallow-rs-fallow -- npx -y fallow mcp-server
What is the Fallow MCP server?
Fallow is an MCP server listed in the public MCP registry as io.github.fallow-rs/fallow. Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools. This page covers its npm package (fallow).
Is the Fallow MCP server safe to use?
Fallow scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Fallow MCP server expose?
Fallow exposes 44 tools: analyze, audit, check_architecture, check_changed, check_health, and 39 more. Their descriptions and schemas cost roughly 30,711 tokens of context every time the server is loaded.
Is the Fallow MCP server still maintained?
Fallow is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Fallow MCP server under?
Fallow declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Fallow MCP server?
VerifyMCP ran 16 checks on Fallow, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.