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
142 of your 234 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 41.32s for a 90.1 MB repo slow.
  • Repobility's analysis ran in 20.44s after the clone landed.

MozillaFoundation/foundation.mozilla.org

https://github.com/MozillaFoundation/foundation.mozilla.org · scanned 2026-06-05 19:56 UTC (4 days, 15 hours ago) · 10 languages

995 raw signals (219 security + 776 graph) 11/13 scanners ran 31st percentile · Python · huge (>500K LoC) System graph score 58 (higher by 13)

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

Complete repo analysis

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

JSON
Combined
67.8
/100
Security checks
77
103 findings
System graph
58
100.0% cov · 370 findings
Critical
0
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 41.0 0.20 8.20
documentation_score 65.0 0.15 9.75
practices_score 100.0 0.15 15.00
code_quality 48.0 0.10 4.80
Overall 1.00 71.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 0 High 26 Medium 42 Low 322 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 103 System graph 370 Crowd 0 Layer: Quality 304 Security 22 Cicd 12 Software 67 Frontend 25 Hardware 4 Api 39

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 3 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.
3 matching findings on this repo
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 4 places repo-level
  • low Near-duplicate function bodies in 3 places repo-level
View all duplicates & near-duplicates findings →
Legacy markers 227 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.
12 matching findings on this repo
  • high [MINED112] FastAPI PATCH foundation_cms.legacy_apps.wagtailpages.pagemodels.blo… foundation_cms/legacy_apps/wagtailpages/tests/blo…:189
  • high [MINED112] FastAPI PATCH foundation_cms.legacy_apps.wagtailpages.pagemodels.blo… foundation_cms/legacy_apps/wagtailpages/tests/blo…:59
  • high [MINED112] FastAPI PATCH foundation_cms.legacy_apps.events.views.basket has no … foundation_cms/legacy_apps/events/tests.py:55
  • low File has no detected symbols: frontend/legacy/playwright.config.js
  • low File has no detected symbols: frontend/legacy/tailwind.config.js
  • low File has no detected symbols: frontend/legacy/eslint.config.js
  • low File has no detected symbols: frontend/legacy/postcss.config.js
  • low File has no detected symbols: frontend/legacy/lint-js.js
  • low File has no detected symbols: frontend/legacy/tailwind-plugins/button.js
  • low File has no detected symbols: frontend/legacy/tailwind-plugins/components.js
  • low File has no detected symbols: frontend/legacy/tests/mozfest-urls.js
  • low File has no detected symbols: frontend/legacy/tests/base-urls.js
View all legacy markers findings →
Commented-out code 16 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 frontend/legacy/tailwind-plugins/form-control…
  • info Commented-code block (8 lines) in foundation_cms/urls.py:115
  • info Commented-code block (6 lines) in foundation_cms/settings/base.py:660
  • info Commented-code block (8 lines) in foundation_cms/legacy_apps/static/js/componen…
  • info Commented-code block (6 lines) in foundation_cms/legacy_apps/wagtailpages/templ…
  • info Commented-code block (8 lines) in foundation_cms/legacy_apps/wagtailpages/facto…
  • info Commented-code block (6 lines) in foundation_cms/legacy_apps/wagtailpages/migra…
  • info Commented-code block (5 lines) in foundation_cms/legacy_apps/wagtailpages/pagem…
  • info Commented-code block (6 lines) in foundation_cms/legacy_apps/wagtailpages/pagem…
  • info Commented-code block (7 lines) in foundation_cms/legacy_apps/wagtailpages/pagem…
  • info Commented-code block (6 lines) in foundation_cms/legacy_apps/wagtailpages/pagem…
  • info Commented-code block (5 lines) in foundation_cms/static/js/components/expert_hu…
View all commented-out code findings →
Config drift 14 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
  • low File has no detected symbols: frontend/redesign/playwright.config.js
  • low File has no detected symbols: frontend/redesign/eslint.config.js
  • low File has no detected symbols: frontend/redesign/postcss.config.js
  • low File has no detected symbols: frontend/legacy/playwright.config.js
  • low File has no detected symbols: frontend/legacy/tailwind.config.js
  • low File has no detected symbols: frontend/legacy/eslint.config.js
  • low File has no detected symbols: frontend/legacy/postcss.config.js
  • low Stray `console.log` in TS/JS — frontend/redesign/esbuild.config.js:17
  • info TODO/FIXME marker in shipping code — frontend/legacy/tailwind.config.js:284
  • low Stray `console.log` in TS/JS — frontend/legacy/esbuild.config.js:20
  • low Very large file: foundation_cms/legacy_apps/donate/migrations/0005_configure_ca…
  • low Very large file: foundation_cms/legacy_apps/mozfest/migrations/0044_configure_c…
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/dc250080-d267-4bf9-ac32-2a9943ec5c3e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/dc250080-d267-4bf9-ac32-2a9943ec5c3e/

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.