fallow-rs/fallow

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

25 of your 96 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 3.51s · analysis 104.94s · 18.0 MB · GitHub preflight 460ms

https://github.com/fallow-rs/fallow · scanned 2026-06-05 13:19 UTC (5 days, 7 hours ago) · 10 languages

686 raw signals (86 security + 600 graph) 60th percentile · Typescript · large (100-500K LoC) System graph score 63 (higher by 13)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 7 hours ago · v2 · 364 actionable findings from 2 signal sources. 22 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 291 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	52.0	0.25	13.00
`testing_score`	100.0	0.20	20.00
`documentation_score`	98.7	0.15	14.80
`practices_score`	86.0	0.15	12.90
`code_quality`	65.8	0.10	6.58
Overall		1.00	76.3

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 13 Medium 26 Low 269 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 73 System graph 291 Crowd 0 Layer: Quality 122 Software 99 Security 2 Cicd 3 Frontend 135 Network 3

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Legacy markers 1 finding

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

1 matching finding on this repo

low File has no detected symbols: tests/fixtures/tanstack-router-conventions/src/ro…

View all legacy markers findings →

Commented-out code 32 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (8 lines) in editors/vscode/src/download.ts:186
info Commented-code block (5 lines) in editors/vscode/src/coverageCommand.ts:126
info Commented-code block (6 lines) in editors/vscode/src/extension.ts:133
info Commented-code block (6 lines) in editors/vscode/src/commands.ts:474
info Commented-code block (6 lines) in editors/vscode/src/types.ts:16
info Commented-code block (6 lines) in editors/vscode/src/generated/output-contract.…
info Commented-code block (6 lines) in tests/fixtures/issue-843-nestjs-lifecycle/src…
info Commented-code block (5 lines) in tests/fixtures/issue-605-new-class-member/src…
info Commented-code block (6 lines) in tests/fixtures/issue-605-new-class-member/src…
info Commented-code block (5 lines) in tests/fixtures/issue-317-namespace-barrel-ign…
info Commented-code block (5 lines) in tests/fixtures/issue-328-namespace-object-ali…
info Commented-code block (5 lines) in tests/fixtures/issue-346-static-factory-metho…

View all commented-out code findings →

Config drift 22 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

12 matching findings on this repo

info npm package `@commitlint/config-conventional` is patch version(s) behind (21.0.… package.json
low File has no detected symbols: editors/vscode/test/configKeys.test.ts
low File has no detected symbols: editors/vscode/test/config.test.ts
low File has no detected symbols: tests/fixtures/issue-399-new-url/vite.config.ts
low File has no detected symbols: tests/fixtures/issue-623-vite-react-compiler-cont…
low File has no detected symbols: tests/fixtures/webpack-alias-project/webpack.conf…
low File has no detected symbols: tests/fixtures/docusaurus-theme-only-conventions/…
low File has no detected symbols: tests/fixtures/nuxt-custom-dirs/nuxt.config.ts
low File has no detected symbols: tests/fixtures/nuxt-content-config/nuxt.config.ts
low File has no detected symbols: tests/fixtures/nuxt-content-config/content.config…
low File has no detected symbols: tests/fixtures/nuxt-content-config/extra/unused.ts
low Stray `console.log` in TS/JS — tests/fixtures/issue-820-vercel-ts-config/src/in…

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/d8262f50-e393-4de5-ada5-d67b4a70b23a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d8262f50-e393-4de5-ada5-d67b4a70b23a/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.