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.

suprabho/vismay

https://github.com/suprabho/vismay · scanned 2026-06-16 00:26 UTC (2 months, 2 weeks ago)

579 raw signals (0 security + 579 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 115 Medium 70 Low 177 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 573 Crowd 0 Layer: Software 4 Frontend 173 Security 15 Quality 222 Api 159

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 1 finding

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.

1 matching finding on this repo

low Near-duplicate function bodies in 2 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 `previewLegacy` in packages/content-source/src/hand…

View all legacy markers findings →

Commented-out code 123 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 f1_backend/AI/app/main.py:347
info Commented-code block (5 lines) in f1_backend/AI/app/pipelines/story_crew.py:228
info Commented-code block (5 lines) in apps/vizf1/web/components/RaceCardExpandable.…
info Commented-code block (6 lines) in apps/vizf1/web/lib/useFollowedEntities.ts:30
info Commented-code block (5 lines) in apps/catalog/components/ModuleCard.tsx:27
info Commented-code block (5 lines) in apps/footshorts/shared/src/editorial.ts:132
info Commented-code block (6 lines) in apps/footshorts/worker/src/recap.ts:503
info Commented-code block (6 lines) in apps/footshorts/worker/src/fixtures.ts:218
info Commented-code block (5 lines) in apps/footshorts/mobile/tailwind.config.ts:9
info Commented-code block (6 lines) in apps/footshorts/mobile/babel-plugins/skip-cod…
info Commented-code block (5 lines) in apps/footshorts/mobile/src/components/AuraBac…
info Commented-code block (5 lines) in apps/footshorts/mobile/src/components/ForYouM…

View all commented-out code findings →

Config drift 9 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.

9 matching findings on this repo

info `truncate` class without `title=` for hover reveal — apps/admin/components/vizm…
critical Possible secret in f1_backend/Frontend/src/config/firebase.ts f1_backend/Frontend/src/config/firebase.ts:5
info Commented-code block (5 lines) in apps/footshorts/mobile/tailwind.config.ts:9
info Commented-code block (5 lines) in apps/vizmaya-fyi/next.config.ts:14
info Commented-code block (7 lines) in apps/vizmaya-fyi/lib/storyReportConfig.ts:322
info Commented-code block (6 lines) in apps/admin/next.config.ts:4
info Commented-code block (6 lines) in packages/content-source/src/storyConfig.ts:138
high Dangling fetch: GET /api/stories/configs (apps/vizmaya-fyi/components/map-edit/…
high Dangling fetch: POST /api/story-report-config/${slug} (apps/vizmaya-fyi/compone…

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/6943eea4-985b-4136-b459-f4f1369a4965/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6943eea4-985b-4136-b459-f4f1369a4965/

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.