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.

tranchistudio-sys/studio

https://github.com/tranchistudio-sys/studio · scanned 2026-06-16 00:41 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 · 317 actionable findings from 1 signal source. 11 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 · 317 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 7 Medium 71 Low 172 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 317 Crowd 0 Layer: Frontend 74 Security 10 Cicd 2 Quality 174 Api 57

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 (6 lines) in lib/db/src/schema/staff_payroll.ts:51
info Commented-code block (6 lines) in lib/api-client-react/src/custom-fetch.ts:111
info Commented-code block (5 lines) in artifacts/api-server/build.mjs:25
info Commented-code block (10 lines) in artifacts/api-server/scripts/check-duplicate…
info Commented-code block (5 lines) in artifacts/api-server/src/migrations.ts:693
info Commented-code block (6 lines) in artifacts/api-server/src/follow-up-scheduler.…
info Commented-code block (10 lines) in artifacts/api-server/src/lib/overtime.ts:1
info Commented-code block (6 lines) in artifacts/api-server/src/lib/objectAcl.ts:7
info Commented-code block (6 lines) in artifacts/api-server/src/routes/revenue.ts:1
info Commented-code block (8 lines) in artifacts/api-server/src/routes/storage.ts:170
info Commented-code block (9 lines) in artifacts/api-server/src/routes/notifications…
info Commented-code block (6 lines) in artifacts/api-server/src/routes/ai-engine.ts:…

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 Runtime service client appears to use placeholder configuration

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/e57d7693-571b-4b58-9c18-99c1fc342400/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e57d7693-571b-4b58-9c18-99c1fc342400/

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.