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.

thomaspryor/Broadwayscore

https://github.com/thomaspryor/Broadwayscore · scanned 2026-06-16 00:37 UTC (2 months, 2 weeks ago)

2224 raw signals (0 security + 2224 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 1719 actionable findings from 1 signal source. 505 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 · 1719 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 144 Medium 316 Low 835 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 1719 Crowd 0 Layer: Frontend 930 Network 5 Security 172 Cicd 4 Quality 466 Api 142

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 2 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.

2 matching findings on this repo

low Old/deprecated-named symbol `expectedLegacy` in scripts/validate-ab-test.js:216
low Old/deprecated-named symbol `nLegacy` in scripts/export-cookies.js:186

View all legacy markers findings →

Commented-out code 350 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 next.config.js:22
info Commented-code block (5 lines) in tests/unit/is-includable-for-rebuild.test.mjs…
info Commented-code block (9 lines) in tests/unit/review-write-guard-topology.test.m…
info Commented-code block (5 lines) in tests/unit/playbill-verdict-discover.test.mjs…
info Commented-code block (8 lines) in tests/unit/is-likely-stale-wrong-show.test.mj…
info Commented-code block (6 lines) in tests/unit/wrong-production-rebuild-guard.tes…
info Commented-code block (7 lines) in tests/unit/backfill-html-override-rename.test…
info Commented-code block (7 lines) in tests/unit/collect-review-texts-rename-helper…
info Commented-code block (5 lines) in tests/unit/url-content-sanity.test.mjs:223
info Commented-code block (5 lines) in tests/unit/theater-scorecard-regression.test.…
info Commented-code block (6 lines) in tests/unit/dtli-slug-discover.test.mjs:67
info Commented-code block (6 lines) in tests/unit/review-normalization.test.js:920

View all commented-out code findings →

Config drift 12 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 Stray `console.log` in TS/JS — scripts/regenerate-tier-configs.js:62
low Stray `console.log` in TS/JS — scripts/generate-fantasy-config.js:327
low Very large file: src/config/browse-pages.ts (1113 lines)
medium Runtime service client appears to use placeholder configuration
info Commented-code block (5 lines) in next.config.js:22
info Commented-code block (6 lines) in tests/unit/tier-config-consistency.test.ts:91
info Commented-code block (10 lines) in scripts/llm-scoring/config.ts:40
info Commented-code block (5 lines) in src/config/feature-flags.ts:1
info Commented-code block (5 lines) in src/config/score-buckets.ts:117
info Commented-code block (5 lines) in src/config/outlet-logos.ts:264
info Commented-code block (7 lines) in src/config/scoring.ts:8
info Commented-code block (5 lines) in src/config/guide-pages.ts:521

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/66421544-4165-4be3-9fd2-6c7a7edfbc5c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/66421544-4165-4be3-9fd2-6c7a7edfbc5c/

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.