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
14 of your 82 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 31.22s for a 65.4 MB repo slow.
  • Repobility's analysis ran in 147.39s after the clone landed.

drupal/drupal

https://github.com/drupal/drupal · scanned 2026-05-20 15:21 UTC (2 weeks, 2 days ago) · 10 languages

251 findings (75 legacy + 176 scanner) 11/13 scanners ran Scanner says 90 (lower by 15)

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

Complete repo analysis

Last scanned 2 weeks, 2 days ago · v2 · 163 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
80.9
/100
Repobility
72
75 legacy
9-layer
90
100.0% cov · 88 gaps
Critical
2
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 40.0 0.15 6.00
security_score 100.0 0.25 25.00
testing_score 80.0 0.20 16.00
documentation_score 40.0 0.15 6.00
practices_score 95.0 0.15 14.25
code_quality 80.0 0.10 8.00
Overall 1.00 75.2
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 2 High 23 Medium 25 Low 75 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 75 9-layer 88 Crowd 0 Layer: Quality 89 Security 7 Software 56 Api 1 Frontend 10

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.

Fragile runtime 64 findings
What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.
Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.
How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.
Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).
12 matching findings on this repo
  • medium Suspicious implementation file appears unreferenced core/modules/workspaces/workspaces.post_update.php:1
  • medium Suspicious implementation file appears unreferenced core/modules/views/views.post_update.php:1
  • medium Suspicious implementation file appears unreferenced core/modules/update/update.post_update.php:1
  • medium Suspicious implementation file appears unreferenced core/modules/taxonomy/taxonomy.post_update.php:1
  • medium Suspicious implementation file appears unreferenced core/modules/system/system.post_update.php:1
  • medium Suspicious implementation file appears unreferenced core/modules/node/node.post_update.php:1
  • medium Suspicious implementation file appears unreferenced core/modules/media_library/media_library.post_upd…:1
  • medium Suspicious implementation file appears unreferenced core/modules/media/media.post_update.php:1
  • medium Suspicious implementation file appears unreferenced core/modules/locale/locale.post_update.php:1
  • medium Suspicious implementation file appears unreferenced core/modules/layout_builder/layout_builder.post_u…:1
  • medium Suspicious implementation file appears unreferenced core/modules/help/help.post_update.php:1
  • medium Suspicious implementation file appears unreferenced core/modules/field/field.post_update.php:1
View all fragile runtime findings →
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 Legacy-named symbol `checkLegacy` in core/themes/default_admin/migration/js/ini…
View all legacy markers findings →
Commented-out code 17 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 core/themes/default_admin/js/tableselect.js:43
  • info Commented-code block (5 lines) in core/themes/claro/js/tableselect.js:43
  • info Commented-code block (6 lines) in core/modules/navigation/js/sidebar.js:34
  • info Commented-code block (6 lines) in core/modules/ckeditor5/js/ckeditor5_plugins/d…
  • info Commented-code block (8 lines) in core/modules/ckeditor5/js/ckeditor5_plugins/d…
  • info Commented-code block (6 lines) in core/modules/ckeditor5/js/ckeditor5_plugins/d…
  • info Commented-code block (9 lines) in core/modules/big_pipe/js/big_pipe.js:96
  • info Commented-code block (9 lines) in core/modules/file/js/file.js:224
  • info Commented-code block (6 lines) in core/modules/views_ui/js/views-admin.js:60
  • info Commented-code block (5 lines) in core/modules/toolbar/js/toolbar.menu.js:100
  • info Commented-code block (5 lines) in core/modules/toolbar/js/views/ToolbarVisualVi…
  • info Commented-code block (5 lines) in core/modules/contextual/js/contextual.js:208
View all commented-out code 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/ab12e53b-f3c5-4aa8-b379-78d9cade414d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ab12e53b-f3c5-4aa8-b379-78d9cade414d/

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.