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.
Sign up free Scan another repo
202 of your 327 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 55.1s for a 716.9 MB repo slow.
  • Repobility's analysis ran in 389.83s after the clone landed.

fern-api/fern

https://github.com/fern-api/fern · scanned 2026-06-05 21:46 UTC (4 days, 11 hours ago) · 10 languages

7307 raw signals (315 security + 6992 graph) 11/13 scanners ran 10th percentile · Typescript · huge (>500K LoC) System graph score 40 (higher by 33)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
58.8
/100
Security checks
78
85 findings
System graph
40
100.0% cov · 1053 findings
Critical
5
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 50.0 0.20 10.00
documentation_score 89.0 0.15 13.35
practices_score 69.0 0.15 10.35
code_quality 51.0 0.10 5.10
Overall 1.00 72.8
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 5 High 32 Medium 36 Low 402 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 85 System graph 1053 Crowd 0 Layer: Quality 953 Cicd 11 Software 10 Security 18 Frontend 128 Hardware 3 Api 15

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.

Duplicates & near-duplicates 9 findings
What it is: Same function copy-pasted into multiple modules with minor variations.
Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.
How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.
Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.
9 matching findings on this repo
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 1666 places
  • low Near-duplicate function bodies in 4 places
  • low Near-duplicate function bodies in 185 places repo-level
  • low Near-duplicate function bodies in 370 places
  • low Near-duplicate function bodies in 740 places
  • low Near-duplicate function bodies in 180 places repo-level
  • low Near-duplicate function bodies in 182 places repo-level
  • low Near-duplicate function bodies in 177 places
View all duplicates & near-duplicates findings →
Legacy markers 5 findings
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.
5 matching findings on this repo
  • info TODO/FIXME marker in shipping code — packages/cli/cli-v2/src/docs/server/Legacy…
  • info TODO/FIXME marker in shipping code — packages/cli/cli-v2/src/sdk/generator/Lega…
  • info Commented-code block (5 lines) in packages/generator-cli/src/__test__/replay-le…
  • info Commented-code block (5 lines) in seed/python-sdk/examples/legacy-wire-tests/sr…
  • info Commented-code block (5 lines) in seed/python-sdk/examples/legacy-wire-tests/sr…
View all legacy markers findings →
Commented-out code 518 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 (5 lines) in packages/commons/github/src/ClonedRepository.…
  • info Commented-code block (6 lines) in packages/commons/github/src/parseRepository.t…
  • info Commented-code block (6 lines) in packages/commons/ir-utils/src/__test__/filter…
  • info Commented-code block (5 lines) in packages/commons/api-workspace-commons/src/co…
  • info Commented-code block (5 lines) in packages/commons/core-utils/src/sanitizeChang…
  • info Commented-code block (7 lines) in packages/commons/core-utils/src/validateAgain…
  • info Commented-code block (7 lines) in packages/generator-cli/src/replay/replay-run.…
  • info Commented-code block (5 lines) in packages/generator-cli/src/configuration/sdk/…
  • info Commented-code block (5 lines) in packages/generator-cli/src/__e2e__/chunking-l…
  • info Commented-code block (5 lines) in packages/generator-cli/src/__test__/block-mer…
  • info Commented-code block (5 lines) in packages/generator-cli/src/__test__/replay-le…
  • info Commented-code block (7 lines) in packages/generator-cli/src/__test__/AutoVersi…
View all commented-out code findings →
Config drift 110 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
  • high [MINED131] pre-commit hook `https://github.com/pre-commit/pre-commit-hooks` pin… generators/python/.pre-commit-config.yaml:6
  • info TODO/FIXME marker in shipping code — packages/cli/config/src/schemas/specs/Fern…
  • info TODO/FIXME marker in shipping code — packages/cli/config/src/schemas/specs/Open…
  • info TODO/FIXME marker in shipping code — packages/cli/config/src/schemas/specs/Conj…
  • info TODO/FIXME marker in shipping code — packages/cli/config/src/schemas/specs/Prot…
  • low Stray `console.log` in TS/JS — packages/cli/yaml/loader/src/YamlConfigLoader.ts…
  • info TODO/FIXME marker in shipping code — packages/cli/configuration/src/docs-yml/Pa…
  • info TODO/FIXME marker in shipping code — packages/cli/configuration-loader/src/gene…
  • info TODO/FIXME marker in shipping code — packages/cli/configuration-loader/src/gene…
  • info TODO/FIXME marker in shipping code — packages/cli/configuration-loader/src/gene…
  • low Very large file: packages/cli/configuration-loader/src/generators-yml/convertGe…
  • low Very large file: packages/cli/configuration-loader/src/generators-yml/__test__/…
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/9d3569bc-0fef-45ea-8b24-61a37a6dbd1a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/9d3569bc-0fef-45ea-8b24-61a37a6dbd1a/

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.