fallow-rs/fallow
59.1
Adequate · 14 November 2026
870.3k
lines of production code
Rust
primary language
4
measurements over time
What this system is
Features
Add Vitest plugin for test runner detection and configuration parsing
Introduces a new Vitest plugin that detects Vitest projects (via the 'vitest' or 'vite-plus' dependencies or the presence of vitest/vite config files) and parses their configuration to identify test entry points, setup files, and dependencies. The plugin handles standard vitest.config files as well as vite configs containing a 'test' block, supporting features like named projects, JSX import source rules, and various include patterns.
crates/core/src/plugins/vitest · high confidence
Add fuzzing infrastructure for custom parsers
Added a new fuzzing infrastructure in \fuzz/fuzz\_targets\ with multiple targets (\fuzz\_astro\, \fuzz\_codeowners\, \fuzz\_config\_files\, \fuzz\_config\_glob\, \fuzz\_css\, \fuzz\_extract\, \fuzz\_extract\_cache\, \fuzz\_mdx\, \fuzz\_scripts\, \fuzz\_sfc\, \fuzz\_workspace\_manifests\) to test various parsers and extractors against untrusted input. This includes fuzzing Astro frontmatter and template regions, Codeowners parsing, config file parsing (JSON, TOML) with glob validation, CSS/SCSS extraction, general extraction, extraction caching determinism, MDX statements, script parsing, SFC parsing, and workspace manifest parsing (package.json, pnpm-workspace.yaml).
_fuzz/fuzz\targets · high confidence
Added demo project with sample components and utilities
A new demo project has been added to the assets folder, providing a reference implementation for users. This includes a configuration file (.fallowrc.json) enabling warnings for unused dev dependencies, along with a set of TypeScript source files demonstrating various patterns: React components (Button, Modal, Test), utility functions for formatting dates/currency/percentages and validating emails/phones, service modules for authentication and user retrieval, and type definitions for API responses and legacy configurations.
assets/demo-project · high confidence
Automated VSIX packaging and type-aware sidecar distribution
The VS Code extension now includes a new build pipeline in \editors/vscode/scripts\ that generates platform-specific VSIX packages bundling the type-aware analysis sidecar. This pipeline automatically packages the correct TypeScript backend binaries for each OS and architecture (darwin-arm64, darwin-x64, linux-arm64, linux-x64, win32-arm64, win32-x64) alongside a universal variant, verifies the integrity and executability of the bundled files, and produces a signed inventory manifest with SHA-256 checksums for all artifacts.
editors/vscode/scripts · high confidence
CLI now embeds released skills for offline agent installation
The CLI build process now embeds released skill definitions (such as \fallow\ and \fallow-setup\) directly into the binary. This allows the \fallow agent install\ command to materialize a version-matched copy of these skills even when the project lacks \node\_modules/fallow\, ensuring the agent setup works in isolated or offline environments. A symlink for \schema.json\ is also added to maintain consistency with the project's output schema.
crates/cli · high confidence
Detect unused and unresolved pnpm catalog entries
The tool now analyzes \pnpm-workspace.yaml\ and root \package.json\ files to identify unused catalog entries and unresolved \catalog:\ protocol references in workspace dependencies. It emits \unused-catalog-entries\ findings for catalog versions not referenced by any workspace package (including those with hardcoded consumers) and \unresolved-catalog-references\ for dependencies pointing to non-existent catalog entries, helping users clean up or fix their workspace configurations before running \pnpm install\. The analysis respects pnpm version-specific override behaviors and supports suppression via comments.
_crates/core/src/analyze/unused\catalog · high confidence
Enforce forbidden boundary calls between code zones
The analyzer now detects and reports violations when code in a defined zone calls functions or methods that are explicitly forbidden for that zone. This feature allows you to configure specific zones (e.g., 'domain', 'ui') and define rules that prohibit certain callee patterns (e.g., \console.\*\, \child\_process.exec\) within those zones. The system matches calls against these patterns by checking both the written path and the import-resolved canonical path, ensuring that restrictions apply regardless of how the function is imported. If a zone is defined but no files are classified into it, a warning is issued to prevent silent rule failures.
_crates/core/src/analyze/boundary\calls · high confidence
Expanded script analysis for CI, Git hooks, and test runners
The script analysis module now scans CI configuration files (\.gitlab-ci.yml\ and \.github/workflows/\*.yml\) and Git hook configurations (Husky, Lefthook, lint-staged) to detect binary invocations and file references, ensuring that packages used exclusively in these contexts are credited as used. It also introduces dedicated parsing for built-in test runners (\node --test\, \bun test\, \deno test\) to correctly identify test entry points and apply default file patterns, while adding support for Nx \run-commands\ targets and CLI flag-value dependency crediting via a new embedded TOML catalogue.
crates/core/src/scripts · high confidence
Framework-agnostic template complexity scoring for Astro, Vue, Svelte, and Angular
The \crates/extract/src/template\_complexity\ module now provides a unified, framework-agnostic engine for scoring the complexity of frontend template markup. This engine analyzes JavaScript expressions within template bindings (such as \v-if\, \@if\, \{\#if}\, and attribute bindings) to calculate cyclomatic and cognitive complexity metrics, ensuring consistent scoring across Angular, Vue, Svelte, and Astro. The implementation includes specific scanners for each framework—handling Astro's inline JS expressions, Vue's directive-based control flow, Svelte's logic blocks and snippets, and Angular's template syntax—while masking non-template code like \\<script\>\ and \\<style\>\ blocks to prevent double-counting. This change introduces synthetic \\<template\>\ complexity units that allow users to identify and address high-complexity logic embedded directly within their component views.
_crates/extract/src/template\complexity · high confidence
GitLab CI now posts typed MR comments and inline review discussions
The CI pipeline now uses dedicated Bash scripts to post structured Merge Request comments and inline review discussions to GitLab. These scripts handle authentication via GITLAB\_TOKEN, fetch correct diff references for accurate inline positioning, and render analysis results using the 'fallow' CLI with support for scoping reports to changed files. The implementation includes robust error handling, retry logic for API rate limits, and sidecar marker files to propagate job status (such as skip reasons or deduplication failures) to downstream CI stages.
ci/scripts · high confidence
Initial release of the Fallow VS Code extension
This change introduces the Fallow VS Code extension, providing real-time code intelligence for TypeScript and JavaScript directly in the editor. Users gain access to LSP-powered diagnostics for unused code, duplication, circular dependencies, and complexity, alongside tree views for browsing findings and a status bar for issue counts. The extension supports interactive features such as quick-fix code actions, code lenses for reference counts, and client-side diagnostic muting to reduce noise. It also includes specialized views for project health, security candidates, and runtime coverage, along with commands for auditing changed files and managing licenses. The extension bundles its own LSP client and automatically manages the download of the Fallow CLI binaries.
editors/vscode · high confidence
Introduce @fallow-cli/fallow-node programmatic API
Ship a new Node.js package that exposes fallow's analysis capabilities (dead code, circular dependencies, duplication, similar code, complexity, health, etc.) via a JavaScript API. The package includes native bindings, a loader that resolves companion binaries for type-aware and similar-code analysis, and a build script that generates protocol constants from JSON manifests.
crates/napi · high confidence
Introduce Fallow Zed extension for TypeScript and JavaScript diagnostics
Users can now install the Fallow extension in Zed to receive diagnostics for unused code, dependency issues, and duplication in TypeScript and JavaScript projects. The extension acts as a thin wrapper that launches the existing fallow-lsp binary, supporting automatic binary resolution from local workspaces, PATH, or managed downloads with Ed25519 signature verification. It exposes configuration options for enabling specific diagnostic categories, muting specific issue types, and enabling inline complexity code lenses, providing editor-level feedback that complements the CLI's full health and security reports.
editors/zed · high confidence
Introduce Node.js bindings for programmatic analysis API
This change adds a new NAPI-based interface (\crates/napi/src/lib.rs\) that exposes the underlying analysis engine to Node.js applications. It defines structured options for various analysis modes—including dead code, duplication, similar code, feature flags, and complexity—allowing users to configure parameters such as root paths, thread counts, caching, and specific detection flags (e.g., unused exports, circular dependencies, Svelte/Vue-specific checks) directly from JavaScript/TypeScript code.
crates/napi/src · high confidence
Introduce V8 coverage parsing and UTF-16 offset mapping
Added a new \v8-coverage\ crate that parses V8 \ScriptCoverage\ JSON dumps (emitted by Node, c8, or the Inspector protocol) and converts V8's UTF-16 code-unit source offsets into Istanbul-compatible 1-indexed line and 0-indexed column positions. This provides the foundational data structures (\V8CoverageDump\, \ScriptCoverage\, \LineOffsetTable\) required for the runtime-coverage pipeline, ensuring accurate line/column mapping for sources containing non-ASCII characters.
crates/v8-coverage · high confidence
Introduce \`fallow coverage\` subcommands for runtime coverage analysis and cloud uploads
The CLI now includes a new \fallow coverage\ command group with five subcommands: \setup\ for resumable first-run configuration, \analyze\ for processing local runtime coverage artifacts or fetching data from the Fallow Cloud, \upload-inventory\ for pushing static function inventories, \upload-source-maps\ for uploading build source maps, and \upload-static-findings\ for pushing static dead-code verdicts. This enables users to integrate runtime coverage data with static analysis for a comprehensive view of code health, with explicit support for cloud-based analysis and CI integration.
crates/cli/src/coverage · high confidence
Introduce \`fallow license\` CLI subcommand for license management
The CLI now includes a dedicated \fallow license\ command with subcommands to activate, check status, refresh, and deactivate licenses. Activation supports installing a JWT directly, reading from a file or stdin, or obtaining a 30-day trial via email. The status command displays tier, seats, features, and remaining days. Refresh fetches a new JWT from the API, supporting a fallback to a full-access API key if the current license is missing or stale. All network-bound flows verify the JWT offline using an embedded Ed25519 public key. Output is available in human-readable or JSON formats, with sensitive data like JWTs and API keys redacted in logs.
crates/cli/src/license · high confidence
Introduce comprehensive auto-fix capabilities for dead-code findings
The \fallow fix\ command now automatically applies safe, atomic edits to source files and configuration to remove unused code. This update adds dedicated fixers for unused dependencies (removing entries from \package.json\), unused catalog entries (cleaning \pnpm-workspace.yaml\), unused exports (removing or pruning \export\ statements), unused enum members (folding entire enum declarations when all members are unused), and unused class members. It also introduces a config fixer that automatically adds \ignoreExports\ rules to \.fallowrc.json\ to suppress duplicate export warnings. All fixes are applied with strict safety checks, preserving file encodings (UTF-8 BOM, CRLF/LF), handling dry-run previews, and withholding mutations when analysis confidence is low or the code is referenced off-graph.
crates/cli/src/fix · high confidence
Introduce declarative rule-pack policy engine
The analysis engine now supports configurable rule packs that allow teams to define custom policies for banned calls, imports, exports, and catalogue-derived effects. These rules can be scoped to specific file paths, exclude patterns, and boundary zones, with configurable severity levels and suppression support. The system evaluates these rules against the module graph to report policy violations, enabling enforcement of architectural constraints and coding standards beyond the default linter rules.
crates/core/src/analyze/policy · high confidence
Introduce granular CLI check filtering and rule application
The CLI check command now supports a comprehensive set of \--\<rule-name\>\ flags (e.g., \--unused-exports\, \--private-type-leaks\, \--circular-deps\) that allow users to selectively enable or disable specific issue types during analysis. This change introduces a new \IssueFilters\ struct and a dedicated \filtering\ module that handles both these explicit CLI filters and diff-based scoping (retaining only findings on changed lines). Additionally, the \rules\ module now enforces severity-based filtering, ensuring that findings are suppressed according to the \ResolvedConfig\ rules, including per-file overrides for dead-code and framework-specific issues.
crates/cli/src/check · high confidence
Introduce mutation result caching to skip unchanged mutants
Added a result cache for mutation testing runs that stores outcomes (killed or survived) keyed by a hash of the mutant ID, source file content, covering test details, runner configuration, lockfile, and runtime versions. This allows subsequent runs to skip mutants whose context has not changed, improving performance. The cache is stored in a single JSON file with a configurable maximum entry limit and automatically evicts least recently used entries when full.
_crates/api/src/mutation/result\cache · high confidence
Introduce runtime coverage analysis with signed sidecar verification
The \fallow health\ command now integrates runtime coverage analysis, powered by a dedicated sidecar binary. This new capability includes Ed25519 signature verification for the sidecar binary to ensure integrity, automatic license validation for the feature, and the ingestion of V8 and Istanbul coverage data to identify production coverage gaps. The implementation adds a new \coverage\ module within the health subsystem to handle the complex logic of mapping runtime execution data back to source code, including source map resolution and function identity matching.
crates/cli/src/health · high confidence
Introduce stable type-aware TypeScript analysis sidecar
The \tools/type-aware-sidecar\ now provides a stable, type-aware analysis backend for TypeScript projects. This change introduces a new preflight system to verify that the correct TypeScript version is installed and resolvable, and adds a backend abstraction layer that supports the default TypeScript 7.0.2 API as well as an opt-in experimental \tsrs\ backend. The sidecar's CLI now handles semantic sessions and mutant type-checking operations, while the underlying analysis logic has been updated to correctly handle TypeScript 7.0/7.1 API differences, namespace object uses, computed member access, and Svelte virtual module gaps. Also in this area: 1 commit (1 fix) fixing tools/type-aware-sidecar.
tools/type-aware-sidecar · medium confidence · unverified
Introduce standalone MCP server crate with stdio entry point and static reference resources
The \crates/mcp\ crate now provides the standalone \fallow-mcp\ binary and the \fallow mcp-server\ subcommand, wiring the MCP tool router over stdin/stdout via a dedicated multi-threaded Tokio runtime. The server honors \--version\ flags before starting the stdio handshake and exposes static, read-only reference resources (tool manifest, issue-type registry, explain index, task matrix, and JSON schemas) via the \fallow://\ URI scheme, alongside long-form per-tool guides for \check\_health\ and \get\_cloud\_runtime\_context\. Also in this area: Add opt-in file-length threshold to health checks; Audit tool gains sub-analysis selection and explicit type-aware override; Prop-drilling findings now support CI enforcement and diff-scope placement.
crates/mcp/src · high confidence
Introduce trigger-tree telemetry for documentation discoverability
Added a new \.trigger-tree\ integration to measure which maintainer documentation Codex and Claude Code discover. The setup pins trigger-tree v1.23.2, configures prompt logging to hash-only mode via \config.sh\, and establishes a static discoverability gate (\gate.json\) that enforces a score of 100 on Git-visible documentation structure in CI.
.trigger-tree · high confidence
Introduce type-aware TypeScript analysis transport
Added a new type-aware analysis feature that communicates with a companion sidecar process to provide semantic TypeScript insights. The implementation in \crates/api/src/type\_aware/transport\ handles sidecar discovery (via environment variables or sibling installation), manages persistent and one-shot sessions, and enforces strict security measures such as bounded I/O, environment whitelisting, and path canonicalization to ensure safe execution.
_crates/api/src/type\aware/transport · high confidence
Introduces a new Styling Health score and grade axis
The engine now calculates a dedicated Styling Health score (0–100, letter grade) based on structural CSS analytics, operating as a second axis orthogonal to the existing JS/TS code health. This score evaluates five penalty categories—duplication, dead surface, broken references, token erosion, and structural issues—using a v3 rubric that down-weights exact CSS duplication in favor of detecting value drift and inconsistency. The grade includes a confidence flag that marks the result as low-confidence when the analyzed CSS surface is too sparse (fewer than 50 authored declarations) or predominantly atomic CSS-in-JS, ensuring that thin projects are not penalized unfairly.
_crates/engine/src/health/styling\score · high confidence
LSP server initialization and analysis pipeline
The LSP crate now includes the core server logic for managing editor sessions, running analysis, and publishing diagnostics. This includes session persistence to keep project state between saves, a prewarm phase to load and parse project roots, and the assembly of analysis results (dead code, duplicates, security findings) into LSP diagnostics. It also introduces code actions for suppressing findings and quick-fixes for unused exports, as well as code lenses for export usage counts and React component intelligence.
crates/lsp · high confidence
New CLI binaries for schema emission and test-sidecar stubbing
Two new binaries have been added to the CLI crate: \schema\_emit\ and \stub\_sidecar\. The \schema\_emit\ binary (gated by the \schema-emit\ feature) regenerates the \docs/output-schema.json\ file by deriving definitions from the Rust source of truth, merging them with the committed schema, and printing the resulting JSON Schema to stdout, ensuring the published schema stays in sync with the code. The \stub\_sidecar\ binary is a test-only tool (gated by \test-sidecar-key\) that simulates the closed-source \fallow-cov\ sidecar; it reads requests from stdin and emits responses based on the \FALLOW\_STUB\_MODE\ environment variable, allowing the runtime coverage test harness to exercise the full spawn and marshalling pipeline without depending on the proprietary sidecar.
crates/cli/src/bin · high confidence
New Python scripts for benchmark validation and accuracy evaluation
Added three new Python scripts to support CI and testing workflows: \scripts/check-benchmark-harness.py\ validates that the CodSpeed benchmark matrix, Cargo bench declarations, and Criterion benchmark names remain consistent to prevent CI drift; \scripts/public-config-corpus.py\ fetches public Fallow configuration files from GitHub, analyzes them for workaround signals, and generates a markdown report; and \tests/benchmark-corpus/evaluate-results.py\ computes precision, recall, and F1 scores for duplication detection modes against a ground-truth corpus, serving as a regression tripwire for accuracy.
python · high confidence
New TypeScript type definitions for the Node.js analysis API
The \crates/napi/types\ directory now provides a comprehensive set of TypeScript declaration files (\index.d.ts\) for the Fallow Node.js bindings. This adds strong typing for the programmatic analysis API, covering configuration interfaces such as \AnalysisOptions\, \TypeAwareAnalysisOptions\, and specific analyzers like \DeadCodeOptions\, \ArchitectureOptions\, \DuplicationOptions\, and \ComplexityOptions\. Users of the Node.js integration will now receive IDE autocomplete and compile-time type checking for analysis parameters, including new capabilities like type-aware analysis controls, symlink handling in duplication detection, and granular dead-code flags (e.g., \privateTypeLeaks\, \deprecatedExportsInUse\).
crates/napi/types · high confidence
New architecture boundary and code-quality detectors
The analysis engine now includes several new detectors to enforce architecture and code quality. It can detect imports that cross defined architecture boundary zones without permission (boundary violations) and identify reachable files that are not assigned to any zone (coverage violations). For React and Preact projects, it flags groups of three or more components with identical prop shapes across multiple files, suggesting a missing shared abstraction. In Next.js applications, it detects dynamic-segment name conflicts in the App Router that cause runtime errors, flags 'use client' files that incorrectly export server-only or route-config names, and identifies unused server actions (use-server exports referenced nowhere). Additionally, it now collects and correlates feature flags with dead code findings to highlight unused guarded code.
crates/core/src/analyze · high confidence
New benchmark suite for circular dependencies, duplicate detection, and dead-code analysis
The benchmarks directory now includes a comprehensive suite of scripts to measure performance and accuracy against external tools. \bench-circular.mjs\ compares circular dependency detection against madge and dpdm, while \bench-dupes.mjs\ benchmarks the new duplicate detector against jscpd. A new \bench.mjs\ script compares dead-code analysis against knip, and \compare.mjs\ provides deep comparison of results across multiple issue categories. Additionally, \compare-dupes-rolling.mjs\ evaluates the performance of the rolling duplicate detector, and \cli-instructions.sh\ enables whole-binary instruction counting for CI. The suite is supported by \download-fixtures.mjs\ to fetch real-world projects (including large monorepos like Next.js and Vue) and generators for synthetic circular and duplicate fixtures.
benchmarks · high confidence
New configuration options for architecture boundaries, code duplication, and feature flags
The config crate now supports new sections for defining architecture boundaries (including presets like Layered, Hexagonal, and Bulletproof React), configuring code duplication detection (with options for minOccurrences and ignoreImports), and detecting feature flags via custom SDK patterns. It also introduces validation for user-supplied glob patterns to prevent path traversal and absolute path errors, and adds a finding-ignore matcher to hide specific findings without removing files from the graph.
crates/config/src/config · high confidence
New declarative external plugin system and rule-pack support
The config crate now supports a new external plugin system and declarative rule packs. You can define framework-specific static analysis rules in standalone JSON or JSONC files (rule packs) to ban specific calls, imports, or effects. Additionally, you can register external plugins via TOML, JSON, or JSONC manifests to auto-detect frameworks, define entry points, and configure auto-imports (e.g., for Nuxt components). The crate also introduces a new \config\_writer\ module to safely edit \.fallowrc\ files in place (e.g., for \fallow fix\ actions) and a \fixability\ module to determine if config edits can be applied without fragmenting monorepos. Also in this area: Config schema accepts string or array for extends; config writer preserves trailing commas.
crates/config/src · high confidence
New duplication detection engine with persistent caching and near-miss analysis
The \duplication\_detector\ module has been replaced with a new implementation that introduces a persistent token cache to speed up repeated analysis runs by storing hashed tokens and file metadata, falling back to content comparison when timestamps are unreliable. It adds a bounded near-miss clone detection feature that identifies function-level similarities using MinHash and shingle filtering, and groups clone groups into families with refactoring suggestions (extract function or module) based on shared file sets. The engine now supports semantic detection modes that ignore identifiers and literals, and provides stable, collision-resistant fingerprints for clone groups to enable consistent reporting and trace lookups across runs.
_crates/engine/src/duplication\detector · high confidence
New extract crate modules for asset normalization, complexity, CSS analytics, and feature flags
The \crates/extract/src\ area introduces several new modules that expand the tool's extraction and analysis capabilities. \asset\_url.rs\ adds a \normalize\_asset\_url\ helper to correctly treat bare filenames as relative paths, preventing them from being misclassified as npm packages. \complexity.rs\ implements a new AST visitor to compute per-function cyclomatic and cognitive complexity, including React-specific metrics like hook density and JSX depth. \css.rs\ and \css\_metrics.rs\ provide a hybrid parser for CSS/SCSS files, extracting class names, imports, and structural analytics like specificity and design token usage. \flags.rs\ adds detection for feature flags across various SDKs (LaunchDarkly, Statsig, etc.) and environment variables. Additionally, \astro.rs\ and \glimmer.rs\ add support for extracting logic from Astro frontmatter and Glimmer templates, while \css\_classes.rs\ enables static class token scanning for typo detection.
crates/extract/src · high confidence
New incremental parse cache with bitcode serialization and size caps
The extraction crate now uses a new on-disk cache to store parsed module information, allowing unchanged files to skip AST parsing on subsequent runs. The cache serializes data using the bitcode library and uses xxh3 content hashing to detect changes. It includes write-time size enforcement with LRU eviction to keep the cache file under a configurable cap, and config-aware invalidation to ensure stale data is not reused when extraction settings change. Also in this area: 5 commits (5 fixes) fixing crates/extract; Fixes member access tracking for method return types and adds selector metrics to CSS rules; Fixes to extraction performance, accuracy, and coverage; Fix: String enum members in HTML sink templates are now resolved as literals; Extract Effect layer and error facts, and credit class members that override a base; and 1 more.
crates/extract/src/cache · medium confidence · unverified
New interactive codebase map shell UI
The visualization assets now include a new HTML shell for the codebase map feature. This introduces a dedicated layout with a top bar displaying the 'fallow' brand and project name, a toolbar, a lens summary area, and a main stage that shows a 'Building the map' loading state. A status line at the bottom provides navigation breadcrumbs and keyboard hints (e.g., '/' for search). This change establishes the visual structure for the interactive codebase map interface. Also in this area: Audit now supports file-length complexity thresholds and styling findings ignore line shifts; Enforce explicit error policies for thin wrapper and duplicate prop shape findings.
crates/cli/viz-assets · high confidence
New interactive codebase map visualization
The visualization frontend now includes a new interactive codebase map. This feature introduces a graph-based view of the project, featuring zoomable and pannable navigation, file clustering by directory or import community, and an 'ego' view that highlights a selected file's direct dependencies. The UI includes a toolbar with analysis lenses, a search function, and theme toggling, while the build process now uses Rolldown to bundle the visualization assets. Also in this area: Refactor lazy property setter in payload module.
viz-frontend · medium confidence
New mutation testing engine for JavaScript and TypeScript
The \crates/mutation\ crate introduces a new mutation testing engine that instruments JavaScript and TypeScript source code to detect untested code paths. It supports Vue, Svelte, and Astro component script blocks, and applies mutation operators including arithmetic, relational, logical, and boolean swaps, as well as new operators for regex literals and removing chain links in fluent APIs. The engine skips equivalent mutants to reduce noise, such as logging-only conditions, equivalent case labels, and specific array length comparisons, and provides stable mutant IDs and change descriptions for integration with the test runner.
crates/mutation/tests · high confidence
New programmatic analysis context and audit attribution logic
The API crate now includes a new \ProgrammaticAnalysisContext\ struct that centralizes the resolution of analysis roots, configuration, thread pools, and diff scopes for programmatic consumers, ensuring consistent workspace selection and request outcome tracking. Additionally, new modules for audit attribution (\audit\_keys\, \audit\_complexity\) introduce logic to classify complexity and dead-code findings as introduced or inherited by comparing metric values against a baseline, and the audit output layer now exposes structured verdicts, summaries, and attribution counts (new vs. inherited) in JSON envelopes for programmatic consumers.
crates/api/src · high confidence
New protocol definitions and output contracts for type-aware, similar-code, and mutation analysis
The \crates/output\ crate now includes build-time protocol generation and new output contracts for several analysis capabilities. A new \build.rs\ script reads \type-aware-protocol.json\ and \similar-code-protocol.json\ to generate Rust constants for wire versions, operations, and model artifacts (e.g., \jinaai/jina-embeddings-v2-base-code\), while \mutation-runner-protocol.json\ defines the mutation runner interface (supporting Vitest 4.x–5.x). New output modules expose structured contracts for SARIF duplication and health reporting, audit briefs (schema v13), decision surfaces, diff-risk findings, focus maps, and ownership, enabling richer JSON envelopes and standardized reporting for these features. Also in this area: 2 commits (2 fixes) fixing crates/cli; 1 commit (1 fix) fixing crates/output; Opt-in file-length threshold and Fallow Cloud coverage setup plan; Mutation resume support and CSS template file scanning; Enforce explicit error policies for thin wrapper and duplicate prop shape findings.
crates/output · medium confidence · unverified
New report output formats: shields.io SVG badges, GitHub annotations/summaries, and CodeClimate
The CLI now supports several new report formats. You can generate shields.io-compatible SVG badges for your project health using \--format badge\. For CI integration, \--format github-annotations\ emits GitHub Actions workflow commands, while \--format github-summary\ produces a markdown job summary. Additionally, \--format codeclimate\ outputs issues in the CodeClimate JSON format, compatible with GitLab Code Quality reports.
crates/cli/src/report · high confidence
New rule-pack templates and agent onboarding scaffolding
The CLI now ships with five new rule-pack templates (ai-safe-repo, clean-architecture, next-app-router, side-effect-free-domain, starter) to help teams enforce architectural and security policies out of the box. Additionally, the \fallow agent\ command now includes a new onboarding flow that scaffolds \AGENTS.md\ and \CLAUDE.md\ files and registers the \fallow-mcp\ server with supported coding agents (Claude, Codex, Cursor), including a PreToolUse gate script to ensure agents run analysis before editing.
crates/cli/src · high confidence
New visitor module for AST-based module extraction
The \crates/extract/src/visitor\ directory has been introduced to handle the AST-based extraction of module information. This new module includes helpers for Angular component metadata, React/JSX structural extraction, and a comprehensive visitor implementation that tracks exports, imports, class members, and framework-specific patterns like DI and security sinks. It also includes extensive unit tests to validate the extraction logic. Also in this area: 5 commits (5 fixes) fixing crates/extract; Fixes member access tracking for method return types and adds selector metrics to CSS rules; Fixes to extraction performance, accuracy, and coverage; Fix: String enum members in HTML sink templates are now resolved as literals; Extract Effect layer and error facts, and credit class members that override a base; and 1 more.
crates/extract/src/visitor · medium confidence · unverified
Opt-in TypeScript semantic analysis backend for type-aware checks
The API now supports an opt-in TypeScript semantic analysis backend (controlled via the FALLOW\_TYPE\_AWARE\_BACKEND environment variable) to provide deeper type-aware insights. This change introduces a shared client module that manages the lifecycle of the semantic companion, including subprocess discovery, request validation, and result reconciliation. It specifically enables refining dead-code detection results using semantic data and adds support for type-checking surviving mutants during mutation testing, ensuring that mutations are validated against the TypeScript type system rather than just syntax.
_crates/api/src/type\aware · high confidence
Opt-in hardcoded secret detection and security finding ranking
The security analysis now includes an opt-in detector for hardcoded secrets, identifying static string literals that match provider token shapes or exhibit high entropy corroborated by secret-shaped identifiers. Additionally, security findings are now ranked by runtime reachability, source-backed evidence, and dead-code context to help prioritize the most impactful candidates for verification.
crates/core/src/analyze/security · high confidence
Programmatic API runtime for analysis and audit commands
The API now exposes a dedicated programmatic runtime in \crates/api/src/runtime\ that implements the core logic for dead-code, duplication, health, feature flags, audit, and decision-surface analyses. This runtime provides typed entry points (e.g., \run\_dead\_code\, \run\_audit\, \run\_combined\) that return structured programmatic outputs, enabling consumers to invoke these analyses without relying on the CLI. The implementation includes support for change-scope filtering, baseline application, and cooperative cancellation via tokens, ensuring that long-running analyses can be stopped cleanly and that results are consistent with the CLI's behavior. Also in this area: 7 commits (3 fixes) modifying crates/cli; Add opt-in file-length threshold and fix styling finding attribution; Mutation testing now supports resuming interrupted runs via an outcome journal.
crates/api/src/runtime · medium confidence · unverified
VS Code extension overhaul with LSP client, tree views, and status bar
The VS Code extension has been rebuilt to provide a richer, more robust analysis experience. It now features a dedicated LSP client for real-time diagnostics, a sidebar tree view for browsing findings, and a status bar for quick access to audit verdicts and health metrics. The extension includes a new baseline command to set analysis scope, improved binary resolution logic to handle local and managed installations, and a single-flight analysis mechanism to prevent race conditions. Users will see enhanced feedback through inline complexity decorations, progressive disclosure of health details, and clearer error handling with automatic backoff on repeated failures.
editors/vscode/src · high confidence
Architecture
Engine now owns core analysis infrastructure and change-scope logic
The engine crate has been refactored to centralize previously scattered responsibilities, introducing new modules for baseline growth comparison, cache status inspection, change coupling and dispersion analysis, change scope resolution, changed-file helpers, Git churn analysis, CI environment detection, and CODEOWNERS parsing. This consolidation means the engine now directly manages how baselines detect growth, how cache health is inspected without running analysis, how Git history is analyzed for hotspots and hidden coupling, how change scopes are resolved and applied, and how file ownership is determined, providing a unified foundation for these capabilities within the engine boundary.
crates/engine/src · high confidence
Health analysis engine restructured into modular pipeline
The health analysis engine in \crates/engine/src/health\ has been refactored into a modular pipeline architecture. The new structure separates concerns into distinct modules: \actions.rs\ handles action context and coverage model selection, \analysis\_data.rs\ prepares shared analysis data and runtime coverage, \assembly.rs\ constructs the final health report and summary, \baseline\_io.rs\ manages baseline save/load with identity-mode guards, \branching.rs\ aggregates per-file branching totals, \change\_coupling\_section.rs\ analyzes change history for hidden coupling, \churn\_file.rs\ validates churn file inputs, \component\_rollup.rs\ synthesizes Angular component complexity rollups, \core\_pipeline.rs\ orchestrates the main health pipeline, \coverage\_gaps.rs\ scans for untested exports, and \coverage\_intelligence.rs\ builds coverage intelligence findings. This restructuring improves code organization and maintainability of the health analysis system.
crates/engine/src/health · high confidence
Human report rendering is modularized into dedicated submodules
The human-readable report output logic has been reorganized from a monolithic structure into distinct, focused submodules (check, cross\_ref, dupes, health, health\_hotspots, health\_runtime, health\_targets, perf, traces, and walkthrough). This change improves code maintainability and readability by separating the rendering concerns for different analysis categories—such as dead code, duplication, health metrics, and performance timings—into their own files, while preserving the existing user-facing output format and behavior.
crates/cli/src/report/human · high confidence
Refactored import resolution into a modular, session-based architecture
The import resolution engine in \crates/graph/src/resolve\ has been restructured into distinct submodules (\static\_imports\, \dynamic\_imports\, \require\_imports\, \re\_exports\, \fallbacks\, etc.) to improve maintainability and testability. This change introduces a \ResolverSession\ struct that caches expensive setup state (such as workspace canonicalization and resolver construction), allowing callers to reuse this state across multiple resolution runs for better performance. The refactoring also adds specific fallback strategies for SCSS partials, CSS extensions, and path aliases, while ensuring that dynamic imports and CommonJS \require\ calls are resolved uniformly into the graph's internal representation.
crates/graph/src/resolve · high confidence
Behavioural changes
1 commit (0 fixes) modifying packaging/crates-io/fallow
A change to existing behaviour in packaging/crates-io/fallow — 1 commit, 1 file: “feat(packaging): add the fallow crate for cargo install fallow (\#4101)” (refs \#4101).
packaging/crates-io/fallow · medium confidence · unverified
104 commits (48 fixes) modifying action/scripts
A change to existing behaviour in action/scripts — 104 commits (48 fixs), 16 files: “fix(action): handle multiple JSON objects in bare invocation output”; “refactor: remove duplicate helpers, stale text and vacuous tests (\#3097)”; “feat(action): post PR output as the branded Fallow app (\#1737)”; and 101 more (refs \#3097, \#1737, \#4082, \#2693, \#2562, …).
action/scripts · medium confidence · unverified
13 commits (4 fixes) modifying crates/cli/src/schema
A change to existing behaviour in crates/cli/src/schema — 13 commits (4 fixs), 2 files: “refactor(cli): share the gate map and the exit code constants (\#4166)”; “feat(dead-code): add the opt-in constant-parameter rule (\#4494)”; “feat(health): add an opt-in file-length threshold (maxFileLines) (\#3977)”; and 10 more (refs \#4166, \#4494, \#3977, \#4005, \#3724, …).
crates/cli/src/schema · medium confidence · unverified
14 commits (7 fixes) modifying crates/api/src/mutation/companion/runtime
A change to existing behaviour in crates/api/src/mutation/companion/runtime — 14 commits (7 fixs), 16 files: “perf(mutation): stop an endless loop through the active mutant in the companion (\#4353)”; “feat(mutation): add node:test and bun test runner adapters (\#3428)”; “fix(mutation): count the hits of a Node child for its test (\#4356)”; and 11 more (refs \#4353, \#3428, \#4356, \#3994, \#4463, …).
crates/api/src/mutation/companion/runtime · medium confidence · unverified
15 commits (3 fixes) modifying crates/mutation/src
A change to existing behaviour in crates/mutation/src — 15 commits (3 fixs), 13 files: “feat(mutation): show the edit of each mutant in JSON output (\#3717)”; “feat(mutation): mutate component script blocks and regex literals (\#3425)”; “feat(mutation): add operand, quantifier, template and assignment mutants (\#4372)”; and 12 more (refs \#3717, \#3425, \#4372, \#4385, \#4467, …).
crates/mutation/src · medium confidence · unverified
16 commits (7 fixes) modifying crates/cli/src/agent\_install
A change to existing behaviour in crates/cli/src/agent\_install — 16 commits (7 fixs), 9 files: “fix: name the next step on the first run and show the checked review loop (\#3638)”; “refactor(cli): give emit\_error a typed exit code (\#4318)”; “refactor(cli): share the gate map and the exit code constants (\#4166)”; and 13 more (refs \#3638, \#4318, \#4166, \#3107, \#4254, …).
_crates/cli/src/agent\install · medium confidence · unverified
18 commits (5 fixes) modifying crates/api
A change to existing behaviour in crates/api — 18 commits (5 fixs), 5 files: “perf(similar-code): link Accelerate in the macOS companion builds (\#3995)”; “feat(mutation): add node:test and bun test runner adapters (\#3428)”; “feat: harden similar-code agent discovery workflow”; and 15 more (refs \#3995, \#3428, \#4005, \#3994, \#4463, …).
crates/api · medium confidence · unverified
18 commits (8 fixes) modifying crates/process
A change to existing behaviour in crates/process — 18 commits (8 fixs), 7 files: “fix(mcp): bound Code Mode output and single-source its allowlist”; “feat: add stable type-aware TypeScript analysis”; “test(process): bound Windows Job Object teardown by script lifetime (\#3777)”; and 15 more (refs \#3777, \#3480, \#2997, \#4402, \#4333, …).
crates/process · medium confidence · unverified
19 commits (6 fixes) modifying crates/graph/src
A change to existing behaviour in crates/graph/src — 19 commits (6 fixs), 5 files: “refactor: add \#\[must\_use\] to pure functions”; “perf: adopt FxHashMap/FxHashSet for faster hashing”; “chore(lints): require unwrap and expect justifications”; and 16 more (refs \#4402, \#2786, \#773, \#4237, \#4255, …).
crates/graph/src · medium confidence · unverified
2 commits (1 fix) modifying crates/extract/src/flags
A change to existing behaviour in crates/extract/src/flags — 2 commits (1 fix), 3 files: “fix(flags): stop lookalike imports and local functions from certain flag sites (\#3982)”; “refactor: use expect instead of allow for lint suppressions (\#4248)” (refs \#3982, \#4248).
crates/extract/src/flags · medium confidence · unverified
20 commits (7 fixes) modifying crates/engine/src/baseline
A change to existing behaviour in crates/engine/src/baseline — 20 commits (7 fixs), 10 files: “feat(dead-code): add the opt-in constant-parameter rule (\#4494)”; “fix(baselines): stop prune from removing valid entries of a baseline saved in another mode (\#4082)”; “feat(dead-code): report one binding exported under several names (\#4211)”; and 17 more (refs \#4494, \#4082, \#4211, \#3977, \#4222, …).
crates/engine/src/baseline · medium confidence · unverified
24 commits (10 fixes) modifying crates/security/src
A change to existing behaviour in crates/security/src — 24 commits (10 fixs), 7 files: “fix(security): apply overrides rules to security candidates (\#3058)”; “fix(security): report sinks on complex objects, vm bindings and script elements (\#4107)”; “fix(security): gate spawn without a shell like execFile (\#4541)”; and 21 more (refs \#3058, \#4107, \#4541, \#4456, \#4402, …).
crates/security/src · medium confidence · unverified
3 commits (0 fixes) modifying crates/cli/src/coverage/upload\_inventory
A change to existing behaviour in crates/cli/src/coverage/upload\_inventory — 3 commits, 4 files: “feat(coverage): detect Elysia and TanStack Router entry routes (\#4358)”; “feat(coverage): upload the entry routes that can reach each function (\#4122)”; “refactor: use expect instead of allow for lint suppressions (\#4248)” (refs \#4358, \#4122, \#4248).
_crates/cli/src/coverage/upload\inventory · medium confidence · unverified
31 commits (12 fixes) modifying crates/engine/src/mutation
A change to existing behaviour in crates/engine/src/mutation — 31 commits (12 fixs), 12 files: “feat(mutation): show the edit of each mutant in JSON output (\#3717)”; “feat(mutation): mutate component script blocks and regex literals (\#3425)”; “feat(mutation): add operand, quantifier, template and assignment mutants (\#4372)”; and 28 more (refs \#3717, \#3425, \#4372, \#4385, \#4263, …).
crates/engine/src/mutation · medium confidence · unverified
32 commits (15 fixes) modifying crates/api/src/mutation/scheduler
A change to existing behaviour in crates/api/src/mutation/scheduler — 32 commits (15 fixs), 15 files: “fix(mutation): check the run path before a zero-test error counts as a kill (\#3555)”; “fix(mutation): report undiscovered tests as partial, select Vitest config, show progress (\#3608)”; “perf(mutation): stop an endless loop through the active mutant in the companion (\#4353)”; and 29 more (refs \#3555, \#3608, \#4353, \#4350, \#3547, …).
crates/api/src/mutation/scheduler · medium confidence · unverified
368 commits (125 fixes) modifying editors/vscode/src/generated
A change to existing behaviour in editors/vscode/src/generated — 368 commits (125 fixs), 3 files: “feat(security): report client-server-leak runs with no "use client" roots (\#4437)”; “fix(mutation): report undiscovered tests as partial, select Vitest config, show progress (\#3608)”; “feat(dead-code): add a --finding-id filter with a finding\_id\_query answer (\#2987)”; and 365 more (refs \#4437, \#3608, \#2987, \#1701, \#3297, …).
editors/vscode/src/generated · medium confidence · unverified
4 commits (1 fix) modifying crates/cli/src/bin/schema\_emit\_parts
A change to existing behaviour in crates/cli/src/bin/schema\_emit\_parts — 4 commits (1 fix), 2 files: “feat(mutation): rerun the open tasks of a report with fallow mutation --recheck (\#4277)”; “feat(mutation): compare a run with a saved report with fallow mutation --compare (\#4306)”; “fix(schema): prune orphan definitions when the output schema is regenerated (\#4397)”; and 1 more (refs \#4277, \#4306, \#4397, \#4269).
_crates/cli/src/bin/schema\_emit\parts · medium confidence · unverified
4 commits (1 fix) modifying crates/extract/src/component\_contracts
A change to existing behaviour in crates/extract/src/component\_contracts — 4 commits (1 fix), 2 files: “feat: review optional component props absent from callers”; “perf(extract): sort unique component escapes with cached keys (\#3236)”; “fix(absent-props): stop abstaining on method signatures and DOM queries (\#4047)”; and 1 more (refs \#3236, \#4047, \#3843).
_crates/extract/src/component\contracts · medium confidence · unverified
417 commits (114 fixes) modifying scripts
A change to existing behaviour in scripts — 417 commits (114 fixs), 196 files: “chore: remove the review Electron app (\#3709)”; “chore(ci): remove the benchmark dashboard and the metric workflows that CodSpeed replaces (\#3130)”; “chore: integrate Hawk and upgrade Rust to 1.97.1”; and 411 more (refs \#3709, \#3130, \#3594, \#3995, \#3999, …).
scripts · medium confidence · unverified
446 commits (180 fixes) modifying crates/types
A change to existing behaviour in crates/types — 446 commits (180 fixs), 71 files: “feat(security): report client-server-leak runs with no "use client" roots (\#4437)”; “feat: add static feature flag detection (\fallow flags\)”; “fix(mutation): report undiscovered tests as partial, select Vitest config, show progress (\#3608)”; and 443 more (refs \#4437, \#3608, \#3097, \#2987, \#3506, …).
crates/types · medium confidence · unverified
5 commits (0 fixes) modifying crates/multicall
A change to existing behaviour in crates/multicall — 5 commits, 5 files: “test(multicall): fail when a shipped binary builds a full regex DFA (\#3515)”; “chore: block comments that describe the edit history (\#4227)”; “feat(npm): ship one multicall binary per platform package (\#1841)”; and 2 more (refs \#3515, \#4227, \#1841, \#3306, \#2966).
crates/multicall · medium confidence · unverified
5 commits (1 fix) modifying crates/cli/src/viz
A change to existing behaviour in crates/cli/src/viz — 5 commits (1 fix), 2 files: “refactor(cli): give emit\_error a typed exit code (\#4318)”; “refactor(cli): split clap surface and dispatch out of lib.rs (\#3497)”; “feat(health): select groups and track a trend per group (\#3116)”; and 2 more (refs \#4318, \#3497, \#3116, \#2916, \#3280).
crates/cli/src/viz · medium confidence · unverified
52 commits (10 fixes) modifying crates/cli/src/regression
A change to existing behaviour in crates/cli/src/regression — 52 commits (10 fixs), 7 files: “refactor(cli): give emit\_error a typed exit code (\#4318)”; “test: drop low-value CLI tests and test-only helpers (\#2884)”; “feat(stores): cross-graph unused Pinia store member detection (\#1241)”; and 49 more (refs \#4318, \#2884, \#1241, \#4494, \#4211, …).
crates/cli/src/regression · medium confidence · unverified
57 commits (18 fixes) modifying crates/cli/src/report/ci
A change to existing behaviour in crates/cli/src/report/ci — 57 commits (18 fixs), 5 files: “refactor(cli): share the gate map and the exit code constants (\#4166)”; “feat: harden review and reliability workflows (\#1840)”; “feat(stores): cross-graph unused Pinia store member detection (\#1241)”; and 54 more (refs \#4166, \#1840, \#1241, \#2078, \#2959, …).
crates/cli/src/report/ci · medium confidence · unverified
6 commits (0 fixes) modifying tools/similar-code-sidecar
A change to existing behaviour in tools/similar-code-sidecar — 6 commits, 7 files: “refactor(sidecars): remove unreachable checks and pin the guards with runtime tests (\#2791)”; “perf(similar-code): link Accelerate in the macOS companion builds (\#3995)”; “feat: harden similar-code agent discovery workflow”; and 3 more (refs \#2791, \#3995, \#4006).
tools/similar-code-sidecar · medium confidence · unverified
63 commits (30 fixes) modifying crates/api/src/mutation
A change to existing behaviour in crates/api/src/mutation — 63 commits (30 fixs), 31 files: “fix(mutation): check the run path before a zero-test error counts as a kill (\#3555)”; “fix(mutation): report undiscovered tests as partial, select Vitest config, show progress (\#3608)”; “perf(mutation): stop an endless loop through the active mutant in the companion (\#4353)”; and 60 more (refs \#3555, \#3608, \#4353, \#4350, \#3428, …).
crates/api/src/mutation · medium confidence · unverified
65 commits (20 fixes) modifying crates/cli/src/migrate
A change to existing behaviour in crates/cli/src/migrate — 65 commits (20 fixs), 12 files: “chore: integrate Hawk and upgrade Rust to 1.97.1”; “refactor: remove duplicate helpers, stale text and vacuous tests (\#3097)”; “fix: review findings — path traversal, migration hints, JSON output ordering”; and 62 more (refs \#3097, \#2884, \#4166, \#2523, \#4211, …).
crates/cli/src/migrate · medium confidence · unverified
723 commits (221 fixes) modifying npm
A change to existing behaviour in npm — 723 commits (221 fixs), 59 files: “feat(security): report client-server-leak runs with no "use client" roots (\#4437)”; “fix(mutation): report undiscovered tests as partial, select Vitest config, show progress (\#3608)”; “refactor: remove duplicate helpers, stale text and vacuous tests (\#3097)”; and 719 more (refs \#4437, \#3608, \#3097, \#2987, \#1701, …).
npm · medium confidence · unverified
79 commits (39 fixes) modifying tools
A change to existing behaviour in tools — 79 commits (39 fixs), 143 files: “refactor(sidecars): remove unreachable checks and pin the guards with runtime tests (\#2791)”; “fix(mutation): check the run path before a zero-test error counts as a kill (\#3555)”; “perf(similar-code): link Accelerate in the macOS companion builds (\#3995)”; and 76 more (refs \#2791, \#3555, \#3995, \#4353, \#4350, …).
tools · medium confidence · unverified
8 commits (2 fixes) modifying crates/api/src/mutation/kill\_matrix
A change to existing behaviour in crates/api/src/mutation/kill\_matrix — 8 commits (2 fixs), 3 files: “fix(mutation): merge the earlier report into a recheck and replace the --report file (\#4489)”; “feat(mutation): scope baseline-failure to the kill-matrix targets it can affect (\#4476)”; “feat(mutation): check named tests with --kill-matrix-for (\#4165)”; and 5 more (refs \#4489, \#4476, \#4165, \#4373, \#4473, …).
_crates/api/src/mutation/kill\matrix · medium confidence · unverified
8 commits (3 fixes) modifying crates/api/src/similar\_code
A change to existing behaviour in crates/api/src/similar\_code — 8 commits (3 fixs), 5 files: “perf(similar-code): link Accelerate in the macOS companion builds (\#3995)”; “feat: harden similar-code agent discovery workflow”; “feat(api): name the project package manager in the companion install hint (\#4520)”; and 5 more (refs \#3995, \#4520, \#4529, \#4508).
_crates/api/src/similar\code · medium confidence · unverified
Align configuration format with oxlint conventions
The project configuration format has been updated to match oxlint conventions, requiring users to migrate their existing configuration files to the new structure.
(repo-wide) · high confidence
Audit attribution now reuses current run as base when changes are non-behavioral
The audit logic now determines whether the current (head) run can serve as the base snapshot for comparison. If all changed files are either cache artifacts, non-behavioral documentation, or JavaScript/TypeScript files with equivalent token streams (ignoring whitespace and comments), the system reuses the head keys as base keys. This avoids creating a separate base worktree and attributes all findings as inherited, streamlining the audit process for cosmetic or cache-only changes. Also in this area: Add opt-in file-length threshold and fix styling finding attribution; Mutation testing now supports resuming interrupted runs via an outcome journal. Also in this area: 2 commits (1 fix) modifying crates/api; 7 commits (3 fixes) modifying crates/cli.
_crates/api/src/audit\run · medium confidence · unverified
CI summaries now use modular jq scripts for annotations, filtering, and reporting
The GitHub Action and GitLab CI summary generation has been refactored from monolithic scripts into a set of modular jq files (annotations-check, annotations-dupes, annotations-health, filter-changed, summary-audit, summary-check). This change introduces precise, file-scoped filtering for PR comments when the 'changed-since' mode is active, ensuring annotations only appear for modified files while preserving project-wide dependency findings in the total count. It also standardizes the output format for annotations and audit summaries, adding support for new finding types such as boundary violations, policy violations, Next.js directive issues, and pnpm catalog errors, while improving clarity with caveats for findings based on incomplete file reads.
action/jq · high confidence
CSS analytics engine refactored into modular submodules
The CSS analytics logic in the health engine has been reorganized from a single large module into dedicated submodules (\classes\, \cva\, \markup\_scan\, \near\_duplicates\, \preprocessor\, \theme\_tokens\, \token\_consumers\). This structural change introduces specific new capabilities: \classes.rs\ adds detection of likely class-name typos in markup by comparing tokens against defined CSS classes; \cva.rs\ adds detection of duplicate variant blocks and token drift in Class Variance Authority (CVA) usage; and \preprocessor.rs\ adds a virtual stylesheet generator that flattens Sass/Less parent selectors to improve metric accuracy. The refactoring also introduces \StylingAnalysisArtifacts\ to cache styling data for reuse across health, audit, and editor surfaces.
_crates/engine/src/health/css\analytics · high confidence
CSS-in-JS styling analytics now support object notation and design tokens
The styling-health analytics pipeline now covers CSS-in-JS libraries that use object-literal styles (StyleX, Panda, vanilla-extract, and emotion) in addition to the previously supported tagged-template forms. Object-style styles are serialized into virtual stylesheets and split into three categories—structural, structural-partial, and atomic—so the engine can correctly apply duplicate-detection and structural-grade policies depending on whether the library produces flat atomic CSS. The pipeline also extracts design-token definitions and cross-module consumer usage for StyleX, vanilla-extract, and Panda, enabling token blast-radius analysis. These changes are health-time-only and do not affect the extraction cache.
_crates/extract/src/css\_in\js · high confidence
Core engine refactoring and new analysis capabilities
The core analysis engine has been significantly restructured: the monolithic analyze.rs, discover.rs, graph.rs, and resolve.rs modules have been removed and replaced with a new plugin-based architecture and extracted crates (fallow-extract, fallow-graph). This change introduces a new error handling system (FallowError) with actionable help text and error codes, a new suppression context that tracks used vs. stale suppressions, and new capabilities for detecting external style package usage and managing git environment variables to prevent hook-related failures. Additionally, a new progress spinner UI has been added for the analysis pipeline, and package asset patterns for scaffolding templates are now automatically derived from package.json files.
crates/core/src · high confidence
Graceful shutdown and orphan process reaping on Ctrl+C
The CLI now installs signal handlers for SIGINT/SIGTERM (Unix) and console control events (Windows) to prevent orphaned subprocesses when the user interrupts the command. By default, the handler kills all registered child processes, drains them within a bounded time budget, and exits with a standard signal-based exit code (130 for interrupt, 143 for terminate). For the \fallow watch\ command, the CLI enters a cooperative shutdown mode where the handler only signals shutdown, allowing the watch loop to exit cleanly with code 0 while still ensuring in-flight git subprocesses are reaped.
crates/cli/src/signal · high confidence
Graph crate refactored into focused submodules with new analysis capabilities
The graph crate has been restructured from a single large module into focused submodules (ambiguity, build, cycles, effective\_exports, etc.) to improve maintainability and reduce complexity. This refactoring introduces new analysis capabilities including star-export collision detection (ambiguity.rs), circular dependency enumeration via Tarjan's algorithm (cycles.rs), effective export binding resolution with namespace awareness (effective\_exports.rs), and impact-closure computation for change-impact analysis (impact\_closure.rs). The module now provides fan-in/fan-out metrics for blast-radius estimation (fan\_io.rs) and tracks re-export routes for accurate symbol provenance (effective\_re\_exports.rs). These changes enable more precise dead-code detection, better coordination-gap reporting for cross-module changes, and improved handling of complex re-export patterns including star exports and namespace aliases.
crates/graph/src/graph · high confidence
Improved re-export chain resolution and cycle detection
The graph module now features a dedicated re-export propagation system that accurately resolves star and named re-export chains, ensuring references are correctly credited to their original source modules even through complex barrel files. This update introduces explicit detection and reporting of re-export cycles (including self-loops) as user-visible findings, and hardens the resolution logic to prevent silent truncation of re-export chains. Additionally, the system now correctly handles type-only re-exports and ambient module exports, improving the accuracy of unused export detection and reference tracking.
_crates/graph/src/graph/re\exports · high confidence
Introduce isolated OSS Scanner build environment with pinned dependencies
The .oss-scanner directory now includes a Dockerfile and supporting configuration to build the OSS Scanner in an isolated, reproducible environment. The build image pins base images (Rust 1.99.0 and Node.js 22) by SHA-256 digest and installs corepack from a lockfile to ensure deterministic builds. It fetches all Rust crates and npm packages upfront so that subsequent test runs operate offline, and includes a threat model document outlining security properties, untrusted input paths, and severity rating guidelines for the scanner.
.oss-scanner · high confidence
Introduce offline Ed25519 license verification with clock-skew tolerance
The \crates/license\ crate now provides offline JWT verification for the Fallow CLI, enforcing Ed25519 signature validation and rejecting tokens with an \iat\ claim exceeding a 24-hour clock-skew tolerance (configurable via \FALLOW\_LICENSE\_SKEW\_TOLERANCE\_SECONDS\). License material is loaded from environment variables or the user's home directory, and the system exposes a grace period with watermarking for expired licenses before enforcing a hard fail.
crates/license · high confidence
MCP tools now use typed API paths with CLI fallback
The MCP server tools in \crates/mcp/src/tools\ have been refactored to execute analysis commands through a typed programmatic API when parameters map cleanly, falling back to CLI argument construction only for unsupported surfaces like baselines, regressions, or type-aware analysis. This change introduces a new \api\_runtime\ module that handles blocking execution, timeouts, and structured error reporting, while tools like \analyze\, \audit\, and \check\_changed\ now support direct API calls without spawning a subprocess for standard operations, improving performance and reliability for agent-driven workflows.
crates/mcp/src/tools · high confidence
New file, import, and lifecycle analysis predicates
The analysis engine now includes a dedicated \predicates\ module that centralizes detection logic for file types (such as React JSX, TypeScript declarations, HTML, test/spec files, and tooling configuration files), import characteristics (including Node.js/Bun/Deno builtins, virtual modules, path aliases, and implicit dependencies), and framework-specific lifecycle methods (Angular and React). This refactoring consolidates previously scattered checks into reusable functions, ensuring that configuration files are excluded from unused-file reports, virtual modules are not flagged as unresolved imports, and framework-invoked lifecycle methods are correctly identified as used.
crates/core/src/analyze/predicates · high confidence
New framework-specific template scanners for Angular, Glimmer, Vue, and Svelte
The \crates/extract/src/sfc\_template\ module now includes dedicated scanners for Angular, Glimmer, Vue, and Svelte templates. The Angular scanner (\angular.rs\) extracts member references from external HTML files and inline templates, supporting Angular 17+ control flow (\@if\, \@for\, \@defer\) and strict-mode Glimmer/Ember components (\glimmer.rs\) via a custom tokenizer. Vue (\vue.rs\) and Svelte (\svelte.rs\) scanners are refactored to handle Single-File Component (SFC) structures, including typed iteration variables for \v-for\ and \{\#each}\ blocks, and Svelte 5 runes extraction. These changes improve the accuracy of unused member detection by correctly crediting class members and imports referenced in framework-specific template syntax.
_crates/extract/src/sfc\template · high confidence
New suffix array-based duplication detection engine
The duplication detector in \crates/engine/src/duplication\_detector/detect\ has been replaced with a new engine that uses a suffix array and LCP (Longest Common Prefix) approach instead of previous methods. This new implementation concatenates token sequences from all files, builds a suffix array using the linear-time SA-IS algorithm, and extracts clone groups from contiguous LCP intervals, avoiding quadratic pairwise comparisons. The engine includes boundary detection for component-heavy corpora, token ranking and reduction, and sophisticated filtering to remove token/line subsets and atomic invocations. A rolling detector fallback is available for specific corpus types. This change significantly improves performance on large codebases by finding all maximal clones in a single linear pass.
_crates/engine/src/duplication\detector/detect · high confidence
Plugin registry refactored into modular components with expanded built-in plugin support
The plugin registry has been restructured into focused submodules (builtin.rs, helpers.rs, mod.rs, tests.rs) to improve maintainability and performance. This change introduces a comprehensive catalog of built-in plugins for frameworks (Next.js, Nuxt, Remix, Astro, Angular, SvelteKit, etc.), build tools (Vite, Webpack, Rollup, Turborepo), testing frameworks (Vitest, Jest, Playwright, Cypress), and quality tools (ESLint, Biome, Prettier, Tailwind). The refactoring includes performance optimizations such as lazy caching of config matchers and optimized file discovery patterns, while adding extensive test coverage for plugin detection logic including edge cases like production filtering and scoped package matching. Also in this area: 7 commits (7 fixes) fixing crates/core/src; New analysis rules for Effect and improved test entry detection; Support for Alchemy plugin and improved config parsing for Nuxt and tooling.
crates/core/src/plugins/registry · medium confidence · unverified
Pre-bash guard hook prevents unsafe agent commands
A new Python hook at \.claude/hooks/pre-bash-guard.py\ intercepts Bash tool invocations to enforce safer agent behavior. It blocks the use of globally installed \fallow\ binaries, requiring the local \cargo run\ or target binary instead, and prevents unbounded \cargo --workspace\ output from flooding context by enforcing redirection or paging. Additionally, it stops commits that stage VS Code extension runtime files without the corresponding built dist bundle, guiding users to run the necessary build and lint steps first.
.claude/hooks · high confidence
Refactored combined CLI into modular orchestrator and output layers
The combined CLI mode has been restructured into distinct modules (impact, orientation, output) to improve maintainability and separation of concerns. This change introduces a new impact tracking system that records whole-project metrics (dead code, complexity, duplication) only when the run is not narrowed by scope filters or production modes. The output layer now handles both human-readable and machine-readable reports with consistent baseline staleness and issue-failure gating across all formats. The orientation module provides a compact vital signs summary at the start of combined output, showing health scores, dead code percentages, maintainability index, and churn hotspots. Test snapshots have been updated to reflect the new path-based verdict handling in the shared corpus.
crates/cli/src/combined · high confidence
Refactored source discovery into modular entry-point and infrastructure parsers
The source discovery logic in \crates/core/src/discover\ has been restructured into distinct modules (\entry\_points\, \infrastructure\, \parse\_scripts\, \walk\) to improve maintainability and performance. This change introduces dedicated parsing for infrastructure configuration files (Dockerfile, Procfile, fly.toml) to detect external process entry points, and refines \package.json\ script parsing to accurately identify script file references across various runners (node, tsx, bun, etc.). The file walking logic now includes stricter size-based filtering to skip large minified assets and prevents out-of-memory issues by bounding the scan of skipped hidden directories, while also consolidating entry-point deduplication and warning logic.
crates/core/src/discover · high confidence
Fixes
104 commits (79 fixes) fixing crates/graph/src/cache
A fix in crates/graph/src/cache — 104 commits (79 fixs), 2 files: “fix(unused-deps): report direct imports of undeclared workspace packages (\#2990)”; “fix: withhold every mutation the run lacks evidence for”; “fix(eslint): credit extends subpaths and keep root eslintrc discovery (\#4289)”; and 101 more (refs \#2990, \#4289, \#4314, \#3833, \#4422, …).
crates/graph/src/cache · medium confidence · unverified
112 commits (58 fixes) fixing crates/config/src/workspace
A fix in crates/config/src/workspace — 112 commits (58 fixs), 16 files: “feat(catalog): detect and auto-fix empty pnpm catalog groups”; “fix: withhold every mutation the run lacks evidence for”; “feat(catalog): detect unused pnpm catalog entries (\#329)”; and 109 more (refs \#329, \#3788, \#3548, \#3117, \#4221, …).
crates/config/src/workspace · medium confidence · unverified
14 commits (8 fixes) fixing crates/api/src/type\_aware/client
A fix in crates/api/src/type\_aware/client — 14 commits (8 fixs), 6 files: “fix(type-aware): keep a confirmed symbol use complete when evidence is capped (\#4256)”; “feat: add stable type-aware TypeScript analysis”; “fix(type-aware): accept a supported range of tsrs and TypeScript versions (\#4005)”; and 11 more (refs \#4256, \#4005, \#3399, \#3724, \#2095, …).
_crates/api/src/type\aware/client · medium confidence · unverified
16 commits (11 fixes) fixing crates/cli/src/setup\_hooks
A fix in crates/cli/src/setup\_hooks — 16 commits (11 fixs), 3 files: “fix(setup-hooks): tighten install based on live-test feedback”; “fix(hooks): find a project-local fallow and block on a broken launcher (\#4538)”; “fix: harden setup-hooks and baseline defaults”; and 13 more (refs \#4538, \#3289, \#4227, \#3321, \#3105, …).
_crates/cli/src/setup\hooks · medium confidence · unverified
2 commits (2 fixes) fixing crates/core/src/plugins/nuxt, crates/graph
A fix in crates/core/src/plugins/nuxt, crates/graph — 2 commits (2 fixs), 8 files: “fix(nuxt): prefer named \#layers aliases and report missing targets (\#4561)”; “fix: credit declaration siblings, alias targets and Nuxt root layers (\#4539)” (refs \#4561, \#4539).
crates/core/src/plugins/nuxt · medium confidence · unverified
26 commits (16 fixes) fixing crates/api/src/mutation/companion/adapters
A fix in crates/api/src/mutation/companion/adapters — 26 commits (16 fixs), 6 files: “fix(mutation): check the run path before a zero-test error counts as a kill (\#3555)”; “perf(mutation): stop an endless loop through the active mutant in the companion (\#4353)”; “fix(mutation): report duplicate runner test ids and refuse them as kill-matrix targets (\#4350)”; and 23 more (refs \#3555, \#4353, \#4350, \#3428, \#4043, …).
crates/api/src/mutation/companion/adapters · medium confidence · unverified
32 commits (22 fixes) fixing tools/mutation-runner
A fix in tools/mutation-runner — 32 commits (22 fixs), 25 files: “fix(mutation): check the run path before a zero-test error counts as a kill (\#3555)”; “perf(mutation): stop an endless loop through the active mutant in the companion (\#4353)”; “fix(mutation): report duplicate runner test ids and refuse them as kill-matrix targets (\#4350)”; and 29 more (refs \#3555, \#4353, \#4350, \#3428, \#4043, …).
tools/mutation-runner · medium confidence · unverified
351 commits (187 fixes) fixing crates/core/src/plugins
A fix in crates/core/src/plugins — 351 commits (187 fixs), 182 files: “fix(plugins): credit oxlint CLI tooling packages (oxlint-tsgolint) as used (\#802)”; “fix(config): resolve config passed as a named const to a wrapper call”; “refactor: use \#\[expect\] instead of \#\[allow\] for wildcard import suppressions”; and 348 more (refs \#802, \#3180, \#3176, \#4289, \#84, …).
crates/core/src/plugins · medium confidence · unverified
4 commits (4 fixes) fixing crates/config/src/external\_plugin
A fix in crates/config/src/external\_plugin — 4 commits (4 fixs), 2 files: “fix(production): leave out user support entries in production mode (\#4124)”; “fix(plugins): credit the exports that tools read from their config files (\#3730)”; “fix(config): warn about a plugin that can never activate (\#4085)”; and 1 more (refs \#4124, \#3730, \#4085, \#4360).
_crates/config/src/external\plugin · medium confidence · unverified
5 commits (3 fixes) fixing crates/extract/src/astro
A fix in crates/extract/src/astro — 5 commits (3 fixs), 3 files: “fix(health): score functions in Astro script blocks (\#4286)”; “fix: avoid repeated Astro region scanning (\#3878)”; “feat(extract): record function contracts, calls and escapes (\#4475)”; and 2 more (refs \#4286, \#3878, \#4475, \#4565, \#4424).
crates/extract/src/astro · medium confidence · unverified
8 commits (6 fixes) fixing crates/api/src/diff\_risk
A fix in crates/api/src/diff\_risk — 8 commits (6 fixs), 3 files: “fix(audit): count @effect/vitest tests in weakened-tests (\#4167)”; “feat(audit): show the reason of an added fallow-ignore comment (\#4103)”; “fix(audit): feed the brief from diff risk, add the audit MCP guide, align GitLab counts (\#3376)”; and 5 more (refs \#4167, \#4103, \#3376, \#3360, \#3379, …).
_crates/api/src/diff\risk · medium confidence · unverified
9 commits (5 fixes) fixing crates/api/src/mutation/companion
A fix in crates/api/src/mutation/companion — 9 commits (5 fixs), 3 files: “feat(mutation): add node:test and bun test runner adapters (\#3428)”; “fix(mutation): close gaps in the worktree guard and companion cleanup (\#3480)”; “fix(mutation): instrument copied Node sources (\#3994)”; and 6 more (refs \#3428, \#3480, \#3994, \#4463, \#4457, …).
crates/api/src/mutation/companion · medium confidence · unverified
Improved duplication detection for SFCs, Astro, and CSS fragments
The duplication detector now correctly handles Single File Components (Vue/Svelte) and Astro files by extracting and tokenizing their script, template, and style regions separately, ensuring that clones within these distinct sections are identified accurately. Additionally, CSS tokenization has been hardened to canonicalize numeric values (e.g., collapsing \0px\ to \0\) and hex colors (e.g., normalizing \\#FFF\ to \\#ffffff\), allowing the engine to detect near-miss clones that differ only in value formatting. Unparseable code fragments are now assigned their own fingerprints to prevent analysis aborts, and the tokenization strategy distinguishes between preserving file extensions for stable identity and using language modes for function-body parsing.
_crates/engine/src/duplication\detector/tokenize · high confidence
Improved unused-class-member detection for complex access patterns
The unused-class-member analysis in \crates/core/src/analyze/members\ has been refactored into specialized submodules to resolve several false positives where class members were incorrectly reported as unused. The new \factory\ module credits accesses made through static-factory call bindings, free-function factory returns, and object-literal factory returns. The \fluent\_chain\ module now recognizes member accesses within fluent builder chains (both standard and constructor-rooted). The \heritage\ module adds support for Angular external-template member accesses and resolves interface-typed property dispatch through implementers. The \instance\ module fixes inheritance tracking by correctly propagating instance-binding fields from base classes to subclasses. Additionally, the \playwright\ module resolves indexed-access fixture types (e.g., \Factory\["getter"\]\) to their underlying class exports, and the \typed\_property\ module credits accesses reached through typed property hops across module boundaries. Also in this area: Fixes for alias export credits, plugin resolution, and production-only suppressions; New analysis rules for Effect and improved test entry detection; Fixes to factory property origin tracking and callback member analysis. Also in this area: 7 commits (7 fixes) fixing crates/core/src.
crates/core/src/analyze/members · medium confidence · unverified
Symlink CI scripts to shared workspace sources
The vendored CI script templates in the CLI now use symlinks to point to the shared CI scripts in the workspace root. This ensures that updates to the central CI scripts (such as comment.sh, gitlab\_common.sh, and review.sh) are immediately reflected in the CLI templates without requiring separate bundling or duplication.
crates/cli/templates/ci/scripts · high confidence
Test coverage
1 commit adding/updating tests in (repo-wide); 1 commit adding/updating tests in (repo-wide); 1 commit adding/updating tests in (repo-wide); 1 commit adding/updating tests in (repo-wide); 1 commit adding/updating tests in tests/fixtures/angular-component-io-inherited, tests/fixtures/angular-component-io-template-syntax; 1 commit adding/updating tests in tests/fixtures/ci-action-command-inputs, tests/fixtures/yarn-run-top-level-jest/packages/web; 1 commit adding/updating tests in tests/fixtures/class-member-array-field-element, tests/fixtures/class-member-awaited-static-factory, tests/fixtures/class-member-imported-array-factory; 1 commit adding/updating tests in tests/fixtures/class-member-durable-object-stub, tests/fixtures/class-member-utility-type-receivers; 1 commit adding/updating tests in tests/fixtures/constant-parameter; 1 commit adding/updating tests in tests/fixtures/create-require-inline; 1 commit adding/updating tests in tests/fixtures/dupes-vue-sfc-sections; 1 commit adding/updating tests in tests/fixtures/duplicate-export-aliased-wrapper; 1 commit adding/updating tests in tests/fixtures/dynamic-import-const-specifier, tests/fixtures/dynamic-import-suffix-no-extension, tests/fixtures/this-returning-method-chain; 1 commit adding/updating tests in tests/fixtures/graphql-config-documents, tests/fixtures/graphql-config-documents/packages/github, tests/fixtures/pnpmfile-hooks; 1 commit adding/updating tests in tests/fixtures/hoisted-root-plugin-activation/packages/plain, tests/fixtures/hoisted-root-plugin-activation/packages/runner, tests/fixtures/hoisted-root-plugin-activation/packages/web; 1 commit adding/updating tests in tests/fixtures/in-operator-member-probe; 1 commit adding/updating tests in tests/fixtures/issue-4033-this-method-result-local-member; 1 commit adding/updating tests in tests/fixtures/issue-4034-oxlint-js-plugin-dist, tests/fixtures/issue-4034-oxlint-js-plugin-dist/packages/plugin; 1 commit adding/updating tests in tests/fixtures/issue-4183-inherited-this-method-result-member, tests/fixtures/issue-4184-method-call-arguments-chain-member; 1 commit adding/updating tests in tests/fixtures/issue-4198-shadowed-this-method-result-local; 1 commit adding/updating tests in tests/fixtures/issue-4199-class-member-unexported-base; 1 commit adding/updating tests in tests/fixtures/issue-4311-typed-parameter-chain-member, tests/fixtures/issue-4312-unexported-subclass-this-method-result, tests/fixtures/issue-4313-function-array-return-element-member; 1 commit adding/updating tests in tests/fixtures/issue-4351-nested-function-this-member, tests/fixtures/issue-4352-for-of-element-binding-scope; 1 commit adding/updating tests in tests/fixtures/mutation-plan-angular-app-config, tests/fixtures/mutation-plan-build-tool, tests/fixtures/mutation-plan-build-tool-tested-config; 1 commit adding/updating tests in tests/fixtures/namespace-issue-types; 1 commit adding/updating tests in tests/fixtures/new-url-runtime-entry; 1 commit adding/updating tests in tests/fixtures/node-modules-bin-script; 1 commit adding/updating tests in tests/fixtures/npm-alias-pnpm-catalog-binaries/packages/a, tests/fixtures/npm-alias-pnpm-catalog-binaries/packages/b, tests/fixtures/npm-alias-pnpm-catalog-binaries/packages/c; 1 commit adding/updating tests in tests/fixtures/pnpm-nested-workspace-members/packages/app, tests/fixtures/pnpm-nested-workspace-members/site, tests/fixtures/pnpm-nested-workspace-members/site/packages/web; 1 commit adding/updating tests in tests/fixtures/react-native-platform-self-import; 1 commit adding/updating tests in tests/fixtures/react-router-split-route-config; 1 commit adding/updating tests in tests/fixtures/unused-namespace-members, tests/fixtures/unused-namespace-members-reexport; 1 commit adding/updating tests in tests/fixtures/unused-namespace-members-import-type; 1 commit adding/updating tests in tests/fixtures/vite-nested-config/packages/a, tests/fixtures/vite-plus-nested-config/packages/a; 1 commit adding/updating tests in tools/mutation-runner/test/fixtures/vitest-basic/dashboard; 10 commits adding/updating tests in crates/engine/src/duplication\_detector/tokenize/tests; 143 commits adding/updating tests in action/tests; 15 commits adding/updating tests in crates/mcp/tests; 2 commits adding/updating tests in tests/fixtures/effect-schema-exports-as-types; 2 commits adding/updating tests in tests/fixtures/external-override-class-members; 2 commits adding/updating tests in tests/fixtures/nuxt-root-layer-alias; 20 commits adding/updating tests in crates/engine/tests/integration; 269 commits adding/updating tests in crates/cli/tests/integration; 3 commits adding/updating tests in tests/fixtures/security-evasion-shapes; 359 commits adding/updating tests in crates/core/tests; 4 commits adding/updating tests in tests/fixtures/security-catalogue-sinks-882; 4 commits adding/updating tests in tests/fixtures/security-sink-catalogue-gaps; 6 commits adding/updating tests in crates/engine/tests/integration/cache\_model; 6 commits adding/updating tests in tools/mutation-runner/test/fixtures/vitest-basic; 775 commits adding/updating tests in crates/core/tests/integration\_test; Add allocation and large-scale analysis benchmarks; Add component-level benchmark shards for cache, config, engine, graph, output, and programmatic commands; Add sample-app fixture lockfile for review-electron tests; Add semantic clone conformance test corpus; Added Svelte project fixture for testing template and import analysis; Added Vue inject fixture tests for unprovided keys and collision scenarios; Added Vue project fixture for testing SFC template usage; Added benchmarks for duplication detection and similar code analysis; Added compile-time type tests for dead-code detection APIs; Added comprehensive test coverage for the MCP server; Added comprehensive test coverage for the VS Code extension's analysis and diagnostic logic; Added comprehensive unit tests for the extract crate's file-type parsers; Added conformance test fixtures for static analysis edge cases; Added conformance test suite comparing fallow vs knip; Added coverage producer conformance corpus and tests; Added drift contract test harness to verify cross-surface consistency; Added duplication accuracy benchmark harness and baseline; Added ecosystem regression tests for real-world JS/TS projects; Added end-to-end tests for runtime coverage integration; Added fuzzing dictionaries for codeowners, config, extraction, and workspace manifests; Added integration test fixture for optional dependencies; Added integration test fixture for the bulletproof boundary preset; Added integration test fixture for workspace app entry point; Added integration test for package.json \#subpath imports; Added integration test harness for VS Code extension; Added integration tests for API analysis runners and audit behavior; Added integration tests for the VS Code extension; Added real-process integration tests for the VS Code extension; Added security taint analysis test fixtures; Added test corpus for coverage producer geometry; Added test coverage for JavaScript/TypeScript extraction logic; Added test coverage for per-class \this\ binding scoping; Added test coverage for the app package's schema description utility; Added test fixture for Angular Material SCSS entrypoint resolution; Added test fixture for Angular inherited members and DI-injected references; Added test fixture for Angular inject(InjectionToken) template members; Added test fixture for Angular template complexity analysis; Added test fixture for Astro script import extraction; Added test fixture for Bulletproof boundary rules with auto-discovery and strict mode scenarios; Added test fixture for Bun package.json catalogs; Added test fixture for CLI binary name resolution; Added test fixture for CLI package in workspace ancestor manifest scenario; Added test fixture for Express security framework entry-point analysis; Added test fixture for Glimmer TypeScript path aliases; Added test fixture for Jest mock reachability; Added test fixture for Map value class member extraction; Added test fixture for NestJS lifecycle method detection; Added test fixture for ORM and query builder mutation detection; Added test fixture for Pinia setup store helper reads; Added test fixture for Pinia setup store helper reads; Added test fixture for Prettier package.json string configs; Added test fixture for SvelteKit remote function analysis; Added test fixture for Tailwind v4 @plugin directive; Added test fixture for Vite config default export handling; Added test fixture for Vue namespace re-exports; Added test fixture for absent component props; Added test fixture for auto-discover feature boundaries; Added test fixture for awaited async factory class members; Added test fixture for barrel default re-export behavior; Added test fixture for barrel export analysis; Added test fixture for bun.lockb override resolution diagnostic; Added test fixture for cross-file exported class instances; Added test fixture for cross-package enum and class member exports; Added test fixture for dotted export resolution; Added test fixture for dynamic import assigned to existing binding; Added test fixture for dynamic import glob exclusions; Added test fixture for extglob support in import.meta.glob; Added test fixture for factory member return-type annotation handling; Added test fixture for gitignored subpath export resolution; Added test fixture for iconify credit attribution; Added test fixture for ignoring lazy-import cycles; Added test fixture for instanceof-narrowed method calls; Added test fixture for issue \#1441 inferred return member crediting; Added test fixture for local namespace export behavior; Added test fixture for local unexported options class handling; Added test fixture for long fluent builder chains; Added test fixture for merged namespace star re-export; Added test fixture for namespace barrel duplicate exports; Added test fixture for namespace object alias tracking; Added test fixture for native web components detection; Added test fixture for nested .env.schema discovery; Added test fixture for nested barrel export propagation; Added test fixture for new URL filesystem path handling; Added test fixture for ng-packagr entry point parsing; Added test fixture for orphan MDX file detection; Added test fixture for pino transport target configuration; Added test fixture for pnpm bare binary handling; Added test fixture for production-only member suppression; Added test fixture for public API class members; Added test fixture for re-export chain boundary analysis; Added test fixture for same-name schema value dependencies; Added test fixture for satisfies clause usage detection; Added test fixture for security dead-code cross-link analysis; Added test fixture for star re-export chain validation; Added test fixture for static factory method member crediting; Added test fixture for subclass static member usage analysis; Added test fixture for symbol-level call chain analysis; Added test fixture for tracking class member usage through object containers; Added test fixture for type-level enum usage; Added test fixture for type-only import reachability; Added test fixture for type-only namespace extraction; Added test fixture for typed-instance monorepo path-alias scenario; Added test fixture for unreachable mixed exports; Added test fixture for unused re-export detection; Added test fixture for unused signature-backing exports; Added test fixture for useMemo-bound class instance member crediting; Added test fixture for validating stale suppression detection; Added test fixture for webpack inline loader resolution; Added test fixture modules for Bun and Node test script entries; Added test fixtures for Alchemy, Angular, Astro, and architecture boundaries; Added test fixtures for Angular @if aliasing; Added test fixtures for Astro and Lit framework health parity; Added test fixtures for Astro/MDX member expressions and MDX prose environment mentions; Added test fixtures for BoundaryZone subtree-relative patterns; Added test fixtures for CLI integration tests; Added test fixtures for CSS Module global class handling; Added test fixtures for Docusaurus convention coverage; Added test fixtures for Egg.js and Tegg plugin support; Added test fixtures for Firebase Messaging service worker scenarios; Added test fixtures for GitHub Action entry points; Added test fixtures for GraphQL document imports; Added test fixtures for JSDoc import() types and JSX asset references; Added test fixtures for JSX namespace member access; Added test fixtures for Jest and Vitest manual mock semantics; Added test fixtures for Kibana plugin manifests; Added test fixtures for LSP integration testing; Added test fixtures for Lexical custom node lifecycle analysis; Added test fixtures for Next.js 'use client' export validation; Added test fixtures for Next.js App Router route collision detection; Added test fixtures for Next.js route tree collision scenarios; Added test fixtures for Next.js, Nuxt, SvelteKit, Vite, and Vue aliasing and component conventions; Added test fixtures for Node.js test runner default patterns; Added test fixtures for Nuxt auto-imports and virtual module imports; Added test fixtures for Nuxt auto-imports behavior; Added test fixtures for Nuxt component auto-imports and virtual module namespaces; Added test fixtures for Nuxt layer alias scanning; Added test fixtures for ORM source isolation and taint confidence levels; Added test fixtures for Obsidian plugin support; Added test fixtures for OpenNext Cloudflare configuration scenarios; Added test fixtures for OpenTelemetry plugin interface analysis; Added test fixtures for Pinia store member detection; Added test fixtures for Pinia store member detection; Added test fixtures for Playwright test directory and matcher configurations; Added test fixtures for React Compiler configuration; Added test fixtures for React Router route configuration modes; Added test fixtures for React component health analysis; Added test fixtures for React component intelligence and multi-component hook analysis; Added test fixtures for SCSS partial resolution and class inheritance; Added test fixtures for SQL injection detection scenarios; Added test fixtures for Storybook and Vitest entry export detection; Added test fixtures for Storybook stories glob resolution; Added test fixtures for Svelte snippet handling; Added test fixtures for SvelteKit workspace backend and frontend routes; Added test fixtures for TAP and TSD test runners; Added test fixtures for TanStack Router conventions and prefix/ignore patterns; Added test fixtures for TypeScript export and type-scoping scenarios; Added test fixtures for Vite Sass and Vuetify configuration issues; Added test fixtures for Vite plugin usage detection; Added test fixtures for Vite+ plugin scenarios; Added test fixtures for Vitest JSX configuration scenarios; Added test fixtures for Vitest doMock reachability and manual mocks; Added test fixtures for Vitest include scope and nested include behavior; Added test fixtures for Vitest mutation planning; Added test fixtures for Vue SFC export handling; Added test fixtures for Vue and Nuxt edge cases; Added test fixtures for Vue and Vite project analysis; Added test fixtures for Vue, Angular, and Astro iteration binding analysis; Added test fixtures for aliased Sass partial resolution; Added test fixtures for ambient module star re-exports; Added test fixtures for ambient type-star exports; Added test fixtures for ambient type-star exports; Added test fixtures for analysis consistency gaps; Added test fixtures for ancestor manifest dependency resolution; Added test fixtures for architecture boundary violation detection; Added test fixtures for auto-imports and Vue component registration; Added test fixtures for barrel re-export and inheritance scenarios; Added test fixtures for barrel re-export and inheritance scenarios; Added test fixtures for bun and node test runners; Added test fixtures for class callback computed members; Added test fixtures for class producer property analysis; Added test fixtures for client-server leak detection; Added test fixtures for code duplication detection; Added test fixtures for code injection and weak crypto detection; Added test fixtures for command injection and unsafe deserialization security rules; Added test fixtures for complex re-export scenarios; Added test fixtures for constructor-receiver and fluent-chain member usage; Added test fixtures for createRequire function scope and workspace package.json imports; Added test fixtures for cross-file factory class members and opaque destructuring; Added test fixtures for cross-workspace export map resolution; Added test fixtures for dangerous HTML sink detection; Added test fixtures for decorator inheritance, mixed usage, and namespaced decorators; Added test fixtures for deep nested workspace apps; Added test fixtures for deep plugin and module resolution; Added test fixtures for default export credit in plugin config files; Added test fixtures for default export handling with star re-exports; Added test fixtures for default specifier and CSS module handling; Added test fixtures for dependency cycle detection scenarios; Added test fixtures for duplicate exports and peer dependencies; Added test fixtures for duplicate exports and type-only cycles; Added test fixtures for dynamic import and context resolution patterns; Added test fixtures for dynamic import resolution; Added test fixtures for dynamic regex construction detection; Added test fixtures for electron-vite entry point configurations; Added test fixtures for empty flag outputs; Added test fixtures for esbuild external package handling; Added test fixtures for eve-agent-plugin file conventions; Added test fixtures for factory member usage and Pinia store access; Added test fixtures for finding ID generation; Added test fixtures for flag retirement scenarios; Added test fixtures for fluent builder chains and generic-constrained instance bindings; Added test fixtures for framework-aware security sink detection; Added test fixtures for ignoreExportsUsedInFile configuration; Added test fixtures for import analysis scenarios; Added test fixtures for import-equals edge cases; Added test fixtures for import-equals edge cases; Added test fixtures for indexed class value receivers; Added test fixtures for interface and type-alias property hops; Added test fixtures for interface property dispatch; Added test fixtures for issue \#195 scenarios; Added test fixtures for iteration binding in JS and Svelte; Added test fixtures for lib/ package entry mapping; Added test fixtures for misplaced 'use client' directives; Added test fixtures for mocked module reachability scenarios; Added test fixtures for module analysis scenarios; Added test fixtures for multi-hop taint analysis boundaries; Added test fixtures for mutation test reach
analysis; Added test fixtures for named project files and root/directory configuration; Added test fixtures for nestjs-trpc interface implementations; Added test fixtures for new plugin integrations; Added test fixtures for nullish fallback and nullable ternary patterns; Added test fixtures for object-literal factory returns; Added test fixtures for object-map entry configurations; Added test fixtures for oxlint JS plugin configuration parsing; Added test fixtures for oxlint JS plugin directory resolution; Added test fixtures for oxlint configuration file formats; Added test fixtures for package import resolution; Added test fixtures for peer dependency resolution scenarios; Added test fixtures for pkg-utils build-config plugin; Added test fixtures for pnpm package source resolution; Added test fixtures for private field dependency injection; Added test fixtures for private workspace externalized builds; Added test fixtures for private-type-leak detection across multiple frameworks; Added test fixtures for production-only suppression handling; Added test fixtures for re-export cycles; Added test fixtures for resolve call unlisted package detection; Added test fixtures for root dependency credit resolution; Added test fixtures for root-relative static asset resolution; Added test fixtures for route loader data analysis; Added test fixtures for runtime-peer and SSR assertion scenarios; Added test fixtures for secret and PII logging detection; Added test fixtures for security framework entry-point sources; Added test fixtures for security literal sinks (issue 901); Added test fixtures for security origin guard observations; Added test fixtures for security vulnerability detection; Added test fixtures for shadowed class binding members; Added test fixtures for shell helper scripts; Added test fixtures for star-barrel and entry namespace chain analysis; Added test fixtures for star-export ambiguity scenarios; Added test fixtures for subclass member usage analysis; Added test fixtures for suppression inventory command; Added test fixtures for suppression reason validation; Added test fixtures for template-based XSS sinks; Added test fixtures for test-only and production dependencies; Added test fixtures for the reactCompilerPreset configuration; Added test fixtures for tool config loaders; Added test fixtures for tracing react-redux dependency usage; Added test fixtures for tsconfig paths resolution scenarios; Added test fixtures for tsconfig project references; Added test fixtures for tsdown and tsup configuration parsing; Added test fixtures for tsup and tsdown config arrays; Added test fixtures for type-aware analysis; Added test fixtures for type-only import boundary rules; Added test fixtures for under-tested scenarios; Added test fixtures for unknown issue-kind suppression handling; Added test fixtures for unlisted dependencies and workspace shared package; Added test fixtures for unprovided Vue inject and Svelte getContext scenarios; Added test fixtures for unreachable code analysis; Added test fixtures for unused Effect layers and tagged errors; Added test fixtures for unused Svelte component props; Added test fixtures for unused class member detection in Vue, Angular, and plain JS; Added test fixtures for unused code and JSDoc public tag detection; Added test fixtures for unused server actions and misplaced directives; Added test fixtures for unused-file, ORM, and SDK scenarios; Added test fixtures for virtual and workspace mock resolution; Added test fixtures for vitest script config argument; Added test fixtures for whole-object namespace imports; Added test fixtures for workspace binaries and CI working directories; Added test fixtures for workspace credit and peer dependency scenarios; Added test fixtures for workspace dist path aliasing; Added test fixtures for workspace glob configuration handling; Added test fixtures for workspace internal dependencies; Added test fixtures for workspace packages without exports; Added test fixtures for workspace self-references; Added test for rspress @theme virtual module resolution; Added test for skipping irrelevant package scans; Added test suite for GitLab CI installation and bash helpers; Added tests for OpenLayers dispatch and toString coercion; Added tests for Pinia store ReturnType alias resolution; Added tests for SSR module loading with literal paths; Added tests for finding ID filtering and mutation corpus validation; Added tests for scaffold template asset handling; Added tests for spying on specific members of namespace imports; Added unit tests for unused dependency analysis rules; Added utility helper modules to the test fixture workspace; Expanded Next.js fixture coverage for framework conventions; Expanded SvelteKit fixture with route groups and parameterized routes; Expanded fuzzing corpus with fixture seeds for parsers and glob patterns; Expanded test fixtures for open-redirect and SSRF security analysis; New fuzzing infrastructure for path extraction and glob security invariants; New test infrastructure for CLI integration and stub servers.
Dependencies
MCP server migrated to rmcp 2.x
The MCP server implementation in \crates/mcp/src/server\ has been updated to use the rmcp 2.x library. This migration changes the underlying server handler and tool routing infrastructure, which may affect how the server initializes and exposes its tools to clients.
crates/mcp/src/server · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 54 → 59 (+5.1)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.4) — scores are not directly comparable.
Lenses
- Code Health 57 → 58 (+1.6)
- Architecture 88 → 87 (-1.0)
- Maturity 64 → 70 (+6.4)
- Readiness 78 → 92 (+13.2)
- Security 76 → 86 (+9.8)
- Event Sourcing 100 → 100 (+0.0)
- Accessibility 42 → 49 (+6.9)
- Performance 73 → 73 (+0.0)
Resolved (431)
- CacheStore::evict_lru_to_target (cognitive 21) (crates/extract/src/cache/store.rs)
- CacheStore::evict_lru_to_target (cyclomatic 17) (crates/extract/src/cache/store.rs)
- Change coupling: config.ts ↔ treeView.ts (editors/vscode/src/config.ts)
- Change coupling: knip_tables.rs ↔ builtin.rs (crates/cli/src/migrate/knip_tables.rs)
- Change coupling: mod.rs ↔ reachability.rs (crates/graph/src/cache/mod.rs)
- Change coupling: rank.rs ↔ tainted_sink.rs (crates/core/src/analyze/security/rank.rs)
- Change coupling: tainted_sink.rs ↔ visit_impl.rs (crates/core/src/analyze/security/tainted_sink.rs)
- Change coupling: visit_impl.rs ↔ lib.rs (crates/extract/src/visitor/visit_impl.rs)
- Change-coupling hub: mod.rs → compact.rs, markdown.rs, sarif.rs, grouping.rs, health_css.rs (crates/cli/src/health/mod.rs)
- Change-coupling hub: types.rs → html.rs, parse.rs, sfc.rs, angular.rs, vue.rs, template_usage.rs, declarations.rs, helpers.rs, mod.rs, visit_impl.rs, visit_impl_helpers.rs (crates/extract/src/cache/types.rs)
- ClassTooLong: FlagVisitor (crates/extract/src/flags.rs)
- Collector::visit_binary_expression (cognitive 33) (crates/mutation/src/collect.rs)
- Collector::visit_binary_expression (cyclomatic 16) (crates/mutation/src/collect.rs)
- Duplicated block (10 lines × 2) (crates/api/src/dead_code_codeclimate.rs)
- Duplicated block (10 lines × 2) (crates/api/src/dead_code_codeclimate.rs)
- Duplicated block (10 lines × 2) (crates/api/src/markdown_output.rs)
- Duplicated block (10 lines × 2) (crates/cli/src/audit_output.rs)
- Duplicated block (10 lines × 2) (crates/core/src/analyze/prop_drilling.rs)
- Duplicated block (10 lines × 2) (crates/extract/src/parse.rs)
- Duplicated block (10 lines × 2) (crates/extract/src/visitor/visit_impl.rs)
- …and 411 more
New (1067)
- CacheStore::evict_order_range (cognitive 18) (crates/extract/src/cache/store.rs)
- Change coupling: audit_keys.rs ↔ audit_cache.rs (crates/api/src/audit_keys.rs)
- Change coupling: dupes.rs ↔ health.rs (crates/mcp/src/tools/dupes.rs)
- Change coupling: mod.rs ↔ common.mjs (crates/api/src/mutation/scheduler/mod.rs)
- Change coupling: mutation_human.rs ↔ lib.rs (crates/cli/src/mutation_human.rs)
- Change coupling: tainted_sink.rs ↔ template_usage.rs (crates/core/src/analyze/security/tainted_sink.rs)
- Change coupling: tests.rs ↔ common.mjs (crates/api/src/mutation/scheduler/tests.rs)
- Change coupling: unused_exports.rs ↔ unused_files.rs (crates/core/src/analyze/unused_exports.rs)
- Change coupling: verdicts.rs ↔ lib.rs (crates/api/src/mutation/verdicts.rs)
- Change coupling: verdicts.rs ↔ mod.rs (crates/api/src/mutation/verdicts.rs)
- Change-coupling hub: mod.rs → compact.rs, markdown.rs, grouping.rs, health_css.rs (crates/cli/src/health/mod.rs)
- Change-coupling hub: tool_guides.rs → params.rs, mod.rs, mod.rs (crates/mcp/src/tool_guides.rs)
- Change-coupling hub: types.rs → html.rs, parse.rs, sfc.rs, angular.rs, vue.rs, template_usage.rs, declarations.rs, helpers.rs, mod.rs, visit_impl.rs, visit_impl_dynamic_imports.rs, visit_impl_helpers.rs, visit_impl_package_resolution.rs, visit_impl_scope_bindings.rs, visit_impl_signature.rs (crates/extract/src/cache/types.rs)
- ClassTooLong: Collector (crates/extract/src/effect_facts.rs)
- ClassTooLong: FlagVisitor (crates/extract/src/flags/mod.rs)
- ClassTooLong: RulesConfig (crates/config/src/config/rules.rs)
- ClassTooLong: WorkspaceDiagnosticKind (crates/types/src/workspace.rs)
- Collector::bind_held (cognitive 32) (crates/core/src/plugins/config_parser_value_changes.rs)
- Collector::bind_held (cyclomatic 17) (crates/core/src/plugins/config_parser_value_changes.rs)
- Collector::new (cognitive 18) (crates/extract/src/effect_facts.rs)
- …and 1047 more
Changes since last survey
- 300 commits — 150 feature/other, 150 fixes
By area
- crates/cli — 59 commits
- tests/fixtures — 30 commits
- crates/core — 26 commits
- crates/api — 23 commits
- crates/extract — 22 commits
- (root) — 20 commits
- .github/workflows — 14 commits
- .agents/skills — 10 commits
- tools/mutation-runner — 9 commits
- crates/engine — 7 commits
- crates/napi — 6 commits
- editors/vscode — 6 commits
- crates/graph — 5 commits
- crates/mcp — 5 commits
- docs/development — 5 commits
- tools/type-aware-sidecar — 5 commits
- crates/mutation — 4 commits
- npm/fallow — 4 commits
- scripts/type-aware-corpus — 4 commits
- crates/config — 3 commits
Notable commits
- fix: fix(action): contain artifact writes and escape installation diagnostics (#4401)
- fix: fix(action): find detect-libc in the installed package during verification (#4592)
- fix: fix(action): follow the gate in the heading and pin catalog installs (#4534)
- fix: fix(agent): refuse to write through a symlink that leaves the project (#4254)
- fix: fix(angular): credit more template reads and inherited inputs and outputs (#4604)
- fix: fix(audit): compare skip markers, not line text, in skip-only (#4544)
- fix: fix(audit): inherit clone groups that lie inside a base clone group (#4564)
- fix: fix(audit): keep a clone inherited when lines above one copy are rewritten (#4593)
- fix: fix(audit): keep a shifted css-duplicate-block occurrence inherited (#4348)
- fix: fix(baseline): show the cache-dir warning paths with forward slashes on Windows (#4337)
- fix: fix(biome): credit the packages that biome.json extends names (#4537)
- fix: fix(cache): key the graph cache on Bun hoisted versions and Deno installs (#4305)
- fix: fix(cache): key the graph cache on lockfiles and install markers (#4192)
- fix: fix(cache): refuse to write caches through a symlink that leaves the project (#4422)
- fix: fix(cli): correct small output and help defects (#4279)
- fix: fix(cli): name npx fallow in hints when npx started fallow (#4460)
- fix: fix(cli): print no error while a signal ends the process (#4327)
- fix: fix(cli): refuse to write through a symlink that leaves the project (#4410)
- fix: fix(cli): state the owner rule once and link the right cloud on login (#4411)
- fix: fix(config): keep a config file cache.dir inside the project (#4434)
- …and 280 more
Architecture
- Unchanged — 0 containers · 1 contexts · 0 edges
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
fallow-rs/fallow was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 14 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit ae832505075c20912b924e7a770bbadf3d518736 — the exact code this score is about.
- Scored under rubric-2026.11.4 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.65+preprod-3c33c1882dc1.