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.

donghui-0126/StoryQuant

https://github.com/donghui-0126/StoryQuant · scanned 2026-06-17 01:58 UTC (1 month, 1 week ago)

56 raw signals (0 security + 56 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 47 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 14 Low 32 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 47 Crowd 0 Layer: Software 24 Security 8 Cicd 1 Quality 14

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.

Duplicates & near-duplicates 2 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.

2 matching findings on this repo

low Near-duplicate function bodies in 6 places
low Near-duplicate function bodies in 2 places repo-level

View all duplicates & near-duplicates findings →

Legacy markers 6 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.

6 matching findings on this repo

medium Insecure pattern 'cors_wildcard' in legacy/serve.legacy.py:1583 legacy/serve.legacy.py:1583
medium Insecure pattern 'cors_wildcard' in legacy/worker-api.index.js:223 legacy/worker-api.index.js:223
medium Insecure pattern 'direct_innerhtml_assignment' in legacy/src/dashboard/mobile.p… legacy/src/dashboard/mobile.py:423
medium Insecure pattern 'direct_innerhtml_assignment' in legacy/web/app.js:131 legacy/web/app.js:131
low Very large file: legacy/serve.legacy.py (1872 lines)
medium Network/subprocess call without timeout or try/except — legacy/run.py:71

View all legacy markers findings →

Commented-out code 1 finding

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/`.

1 matching finding on this repo

info Commented-code block (6 lines) in serve/markets/base.py:25

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/7bb90d48-f04a-4795-bde8-e9c009cd1863/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7bb90d48-f04a-4795-bde8-e9c009cd1863/

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.