phpbb/phpbb

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.

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

Scan timing: clone 8.49s · analysis 14.66s · 24.7 MB · GitHub preflight 459ms

https://github.com/phpbb/phpbb · scanned 2026-05-20 15:04 UTC (2 weeks, 1 day ago) · 10 languages

216 findings (116 legacy + 100 scanner)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 1 day ago · v2 · 166 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

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	48.8	0.25	12.20
`testing_score`	85.0	0.20	17.00
`documentation_score`	68.6	0.15	10.29
`practices_score`	87.0	0.15	13.05
`code_quality`	50.0	0.10	5.00
Overall		1.00	66.5

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 6 High 82 Medium 12 Low 48 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 116 9-layer 50 Crowd 0 Layer: Cicd 26 Security 11 Software 40 Quality 80 Api 1 Frontend 5 Hardware 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.

Fragile runtime 75 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

low robots.txt does not advertise a sitemap git-tools/merge.php
low [COMP001] High cognitive complexity: Function `process_dir` has cognitive compl… phpBB/develop/remove-php-end-tags.py:53
low [SEC132] String concat where the language has interpolation (AI style drift): S… phpBB/adm/style/permissions.js:119
low Duplicated implementation block across source files phpBB/phpbb/db/extractor/oracle_extractor.php:184
low Duplicated implementation block across source files phpBB/phpbb/db/driver/sqlite3.php:62
low Duplicated implementation block across source files phpBB/phpbb/db/driver/postgres.php:114
low Duplicated implementation block across source files phpBB/phpbb/db/driver/oracle.php:170
low Duplicated implementation block across source files phpBB/phpbb/db/driver/mssqlnative.php:68
low Duplicated implementation block across source files phpBB/phpbb/cron/task/core/tidy_warnings.php:4
low Duplicated implementation block across source files phpBB/phpbb/console/command/user/add.php:63
low Duplicated implementation block across source files phpBB/phpbb/console/command/searchindex/delete.php:1
low Duplicated implementation block across source files phpBB/phpbb/console/command/extension/update.php:31

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 `timezone_copy` in phpBB/assets/javascript/core.js:878

View all legacy markers 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/39acd121-31dd-4d86-b94c-121eecd4031c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/39acd121-31dd-4d86-b94c-121eecd4031c/

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.