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.

Synap-core/backend

https://github.com/Synap-core/backend · scanned 2026-06-16 00:28 UTC (2 months, 2 weeks ago)

399 raw signals (0 security + 399 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 22 Medium 48 Low 163 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 372 Crowd 0 Layer: Frontend 96 Hardware 4 Security 11 Cicd 4 Quality 186 Api 71

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 98 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 apps/api/src/index.ts:15
info Commented-code block (5 lines) in apps/api/src/routers/provision.ts:113
info Commented-code block (5 lines) in apps/pod-admin/middleware.ts:56
info Commented-code block (6 lines) in apps/pod-admin/app/login/LoginForm.tsx:224
info Commented-code block (6 lines) in apps/pod-admin/app/(admin)/workspaces/page.ts…
info Commented-code block (5 lines) in apps/pod-admin/app/(admin)/overview/page.tsx:…
info Commented-code block (5 lines) in deploy/pod-agent/server.js:22
info Commented-code block (5 lines) in packages/types/src/events/index.ts:378
info Commented-code block (6 lines) in packages/types/src/templates/schemas.ts:118
info Commented-code block (6 lines) in packages/auth/src/ory-middleware.ts:72
info Commented-code block (5 lines) in packages/events/src/realtime-schemas.ts:119
info Commented-code block (5 lines) in packages/api/scripts/openapi-smoke.mjs:8

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

medium `fetch()` without try/.catch or AbortSignal — packages/database/src/schema/sour…

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/b67479da-550e-4407-8d51-3167dec7b889/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b67479da-550e-4407-8d51-3167dec7b889/

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.