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

wisdomproto/tangobook

https://github.com/wisdomproto/tangobook · scanned 2026-06-16 00:59 UTC (2 months, 1 week ago)

325 raw signals (0 security + 325 graph)

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

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 325 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
47.5
/100
Security checks
48
0 findings
System graph
48
100.0% cov · 325 findings
Critical
1
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 1 High 38 Medium 88 Low 106 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 325 Crowd 0 Layer: Software 1 Frontend 110 Hardware 3 Security 40 Cicd 2 Quality 84 Api 85

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 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 `__legacy` in packages/client/src/features/longform…
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 (8 lines) in docs/marketing/scripts/audit-noise-and-mine.m…
  • info Commented-code block (9 lines) in docs/marketing/scripts/consolidate-keywords.m…
  • info Commented-code block (5 lines) in scripts/generate-pixar-3d-jack.mjs:1
  • info Commented-code block (5 lines) in scripts/bulk-setup-complete-books.mjs:1
  • info Commented-code block (10 lines) in scripts/audit-v1-storybooks.mjs:3
  • info Commented-code block (7 lines) in scripts/seed-phonics-books.mjs:12
  • info Commented-code block (14 lines) in scripts/migrate-vocabulary-to-keyobjects.mjs…
  • info Commented-code block (16 lines) in scripts/fill-reading-level.mjs:3
  • info Commented-code block (5 lines) in scripts/migrate-korean-phonics-words.mjs:7
  • info Commented-code block (5 lines) in packages/client/src/pages/BookDetailPage.tsx:…
  • info Commented-code block (6 lines) in packages/client/src/features/phonics-learner/…
  • info Commented-code block (5 lines) in packages/client/src/features/games/hooks/useP…
View all commented-out code findings →
Config drift 5 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.
5 matching findings on this repo
  • info `truncate` class without `title=` for hover reveal — packages/client/src/featur…
  • medium Runtime service client appears to use placeholder configuration
  • high Agent instruction/config may expose a secret: packages/client/src/features/mark… packages/client/src/features/marketing/CLAUDE.md:293
  • low Unused endpoint: USE /api/library-config
  • low Unused endpoint: POST /blog/generate-config
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/19e6f46a-b4a8-4fdf-a7c5-a0c6896c80a5/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/19e6f46a-b4a8-4fdf-a7c5-a0c6896c80a5/

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.