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.

Usernode-Labs/social-vibecoding

https://github.com/Usernode-Labs/social-vibecoding · scanned 2026-06-16 00:46 UTC (2 months, 1 week ago)

328 raw signals (0 security + 328 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. 3 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 · 325 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 32 Medium 48 Low 83 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 325 Crowd 0 Layer: Frontend 7 Hardware 5 Security 27 Cicd 1 Quality 203 Api 82

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 161 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 (13 lines) in server.js:53
info Commented-code block (7 lines) in tests/github-issues-route.test.js:3
info Commented-code block (6 lines) in tests/votes-merged-chat-count.test.js:1
info Commented-code block (6 lines) in tests/leaderboard-user-prs.test.js:3
info Commented-code block (5 lines) in tests/spec-wrapper.test.js:1
info Commented-code block (6 lines) in tests/anthropic-stream.test.js:1
info Commented-code block (8 lines) in tests/recovered-turn-push-heal.test.js:3
info Commented-code block (8 lines) in tests/limits-resolve-billing-path.test.js:5
info Commented-code block (5 lines) in tests/edge-gate.test.js:1
info Commented-code block (6 lines) in tests/history.test.js:5
info Commented-code block (9 lines) in tests/issue-creator.test.js:3
info Commented-code block (5 lines) in tests/app-llm-grants.test.js:1

View all commented-out code findings →

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

3 matching findings on this repo

low Stray `console.log` in TS/JS — src/config.js:168
medium Runtime service client appears to use placeholder configuration
info Commented-code block (9 lines) in src/config.js:9

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/9d2420bd-8552-41cd-a12f-aa6669179dfc/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9d2420bd-8552-41cd-a12f-aa6669179dfc/

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.