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.

Clanvaro/unigrc-m-production

https://github.com/Clanvaro/unigrc-m-production · scanned 2026-06-17 01:26 UTC (1 month, 2 weeks ago)

510 raw signals (0 security + 510 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -26.1 (diff) · 463 actionable findings from 1 signal source. 47 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 · 463 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 37 Medium 120 Low 209 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 463 Crowd 0 Layer: Frontend 171 Network 4 Hardware 2 Security 9 Cicd 5 Quality 186 Api 86

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.

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 `buildActionPlanAlertsFromLegacy` in server/action-…

View all legacy markers findings →

Commented-out code 40 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 vite.config.ts:27
info Commented-code block (9 lines) in ecosystem.config.cjs:1
info Commented-code block (6 lines) in tests/unit/chaos-resilience.test.ts:74
info Commented-code block (5 lines) in tests/unit/report-accuracy.test.ts:286
info Commented-code block (5 lines) in tests/unit/residual-risk.test.ts:312
info Commented-code block (5 lines) in tests/unit/backup-restore.test.ts:92
info Commented-code block (6 lines) in tests/unit/zero-downtime-deploy.test.ts:129
info Commented-code block (5 lines) in tests/unit/cascading-deletes.test.ts:116
info Commented-code block (5 lines) in tests/k6/session-token-test.js:146
info Commented-code block (5 lines) in tests/k6/stress-5-users-gcp.js:2138
info Commented-code block (7 lines) in tests/k6/capacity-finding.js:235
info Commented-code block (5 lines) in tests/e2e/api-integration.spec.ts:597

View all commented-out code findings →

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

12 matching findings on this repo

info TODO/FIXME marker in shipping code — vite.config.ts:107
low Stray `console.log` in TS/JS — server/services/unified-cache-config.ts:220
info `truncate` class without `title=` for hover reveal — client/src/pages/config/pr…
medium Runtime service client appears to use placeholder configuration
info Commented-code block (5 lines) in vite.config.ts:27
info Commented-code block (9 lines) in ecosystem.config.cjs:1
low Old/deprecated-named symbol `buildActionPlanAlertsFromLegacy` in server/action-…
medium `fetch()` without try/.catch or AbortSignal — client/src/pages/config/branding.…
medium `fetch()` without try/.catch or AbortSignal — client/src/pages/config/palette.t…
high Dangling fetch: GET /api/coi-public/auth-config (client/src/pages/coi/declaraci…
high Dangling fetch: GET /api/rcsa-public/auth-config (client/src/pages/rcsa/autoeva…
low Unused endpoint: GET /ServiceProviderConfig

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/092f086d-6b6a-48e9-88d6-5ce22bd2135a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/092f086d-6b6a-48e9-88d6-5ce22bd2135a/

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.