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.

bluedotimpact/bluedot

https://github.com/bluedotimpact/bluedot · scanned 2026-06-17 01:42 UTC (1 month, 1 week ago)

167 raw signals (0 security + 167 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -23.9 (diff) · 131 actionable findings from 1 signal source. 36 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 · 131 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 11 High 1 Medium 46 Low 35 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 131 Crowd 0 Layer: Api 1 Frontend 35 Network 2 Hardware 6 Security 29 Cicd 6 Quality 52

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.

Commented-out code 15 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 apps/room/public/display/setup/tampermonkey/g…
info Commented-code block (9 lines) in apps/room/public/display/setup/tampermonkey/b…
info Commented-code block (5 lines) in apps/website/src/server/routers/course-regist…
info Commented-code block (7 lines) in apps/website/src/server/routers/grants.ts:71
info Commented-code block (5 lines) in apps/website/src/server/routers/certificates.…
info Commented-code block (5 lines) in apps/website/src/components/admin/Impersonati…
info Commented-code block (5 lines) in apps/website/src/pages/login/clear.tsx:22
info Commented-code block (5 lines) in apps/infra/src/k8s/serviceDefinitions.ts:388
info Commented-code block (16 lines) in apps/infra/src/k8s/observability.ts:16
info Commented-code block (7 lines) in apps/infra/src/vultr/vke.ts:9
info Commented-code block (9 lines) in apps/pg-sync-service/src/routesPlugin.ts:18
info Commented-code block (7 lines) in apps/pg-sync-service/src/lib/schema-sync.test…

View all commented-out code findings →

Config drift 1 finding

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.

1 matching finding on this repo

low Node manifest has dependencies but no lockfile: libraries/eslint-config/package… libraries/eslint-config/package.json

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/282b719c-02df-4959-bab7-d8b7907e0c2d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/282b719c-02df-4959-bab7-d8b7907e0c2d/

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.