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.

Rynaro/prisma

https://github.com/Rynaro/prisma · scanned 2026-06-15 23:58 UTC (2 months, 3 weeks ago)

53 raw signals (0 security + 53 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 5 Low 17 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 46 Crowd 0 Layer: Network 1 Hardware 2 Cicd 3 Quality 39 Api 1

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 22 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 (7 lines) in apps/github-app/tests/webhook/idempotency.tes…
info Commented-code block (5 lines) in apps/github-app/tests/pipeline/orchestrator.t…
info Commented-code block (5 lines) in apps/github-app/src/main.ts:266
info Commented-code block (5 lines) in apps/github-app/src/server.ts:349
info Commented-code block (5 lines) in apps/github-app/src/worker.ts:177
info Commented-code block (5 lines) in apps/github-app/src/queue/bullmq-job-queue.ts…
info Commented-code block (5 lines) in apps/github-app/src/pipeline/orchestrator.ts:…
info Commented-code block (6 lines) in packages/config/src/config-loader/load.ts:23
info Commented-code block (5 lines) in packages/github/tests/installation-auth/auth.…
info Commented-code block (5 lines) in packages/github/src/publisher/planner.ts:395
info Commented-code block (5 lines) in packages/github/src/publisher/effects.ts:159
info Commented-code block (10 lines) in packages/shared/src/tokens/estimator.ts:3

View all commented-out code findings →

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

2 matching findings on this repo

low Node manifest has dependencies but no lockfile: packages/config/package.json packages/config/package.json
info Commented-code block (6 lines) in packages/config/src/config-loader/load.ts:23

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/28cabd53-494f-44c8-9a30-519d858f7c7a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/28cabd53-494f-44c8-9a30-519d858f7c7a/

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.