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.

jakobng/cinema-scrapers

https://github.com/jakobng/cinema-scrapers · scanned 2026-06-17 01:58 UTC (1 month, 1 week ago)

116 raw signals (0 security + 116 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -11.0 (diff) · 70 actionable findings from 1 signal source. 46 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 4 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.
4 matching findings on this repo
  • low Near-duplicate function bodies in 7 places
  • low Near-duplicate function bodies in 5 places
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 3 places repo-level
View all duplicates & near-duplicates 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 Old/deprecated-named symbol `_merge_eiga_with_legacy` in tokyo/main_scraper.py:…
View all legacy markers findings →
Commented-out code 11 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/`.
11 matching findings on this repo
  • info Commented-code block (7 lines) in north/venue_modules/whitworth_module.py:4
  • info Commented-code block (6 lines) in north/venue_modules/york_art_gallery_module.p…
  • info Commented-code block (5 lines) in north/venue_modules/_twam.py:2
  • info Commented-code block (5 lines) in north/venue_modules/manchester_art_gallery_mo…
  • info Commented-code block (7 lines) in north/venue_modules/bluecoat_module.py:1
  • info Commented-code block (6 lines) in north/venue_modules/sheffield_museums_module.…
  • info Commented-code block (5 lines) in london/cinema_modules/backyard_cinema_module.…
  • info Commented-code block (5 lines) in london/cinema_modules/regent_street_module.py…
  • info Commented-code block (7 lines) in london/cinema_modules/olympic_studios_module.…
  • info Commented-code block (8 lines) in tokyo/cinema_modules/bluestudio_module.py:1
  • info Commented-code block (6 lines) in tokyo/cinema_modules/kino_cinema_module.py:108
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/44628b2e-00f2-4b31-a320-46c85dd151b1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/44628b2e-00f2-4b31-a320-46c85dd151b1/

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.