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: severity: high × 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

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 66.8/100 with 100.0% coverage. It contains 4045 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 328 findings — concentrated in quality (185), frontend (74), api (57). Risk profile is high: 0 critical, 7 high, 82 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 7 of 317 actionable findings. 328 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: GET https://graph.facebook.com/me?fields=id,name&access_token=${encodeURIComponent(cfg.pageAccessToken)} (artifacts/api-server/src/routes/fb-inbox.ts:914)

`artifacts/api-server/src/routes/fb-inbox.ts:914` calls `GET https://graph.facebook.com/me?fields=id,name&access_token=${encodeURIComponent(cfg.pageAccessToken)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET https://graph.facebook.com/me?fields=id,name,fan_count,picture&access_token=${encodeURIComponent(cfg.pageAccessToken)} (artifacts/api-server/src/routes/fb-inbox.ts:897)

`artifacts/api-server/src/routes/fb-inbox.ts:897` calls `GET https://graph.facebook.com/me?fields=id,name,fan_count,picture&access_token=${encodeURIComponent(cfg.pageAccessToken)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/${meData.id}/subscribed_apps?subscribed_fields=messages,messaging_postbacks,messaging_optins,message_deliveries,message_reads&access_token=${encodeURIComponent(cfg.pageAccessToken)} (artifacts/api-server/src/routes/fb-inbox.ts:918)

`artifacts/api-server/src/routes/fb-inbox.ts:918` calls `POST https://graph.facebook.com/${meData.id}/subscribed_apps?subscribed_fields=messages,messaging_postbacks,messaging_optins,message_deliveries,message_reads&access_token=${encodeURIComponent(cfg.pageAccessToken)}` but no backend route matche…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/v22.0/me/messages?access_token=${encodeURIComponent(pageAccessToken)} (artifacts/api-server/src/routes/fb-inbox.ts:194)

`artifacts/api-server/src/routes/fb-inbox.ts:194` calls `POST https://graph.facebook.com/v22.0/me/messages?access_token=${encodeURIComponent(pageAccessToken)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/g…

Dangling fetchFetch

`artifacts/api-server/src/routes/fb-inbox.ts:215` calls `POST https://graph.facebook.com/v22.0/me/messages?access_token=${encodeURIComponent(pageAccessToken)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/g…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/v22.0/me/messages?access_token=${encodeURIComponent(token)} (artifacts/api-server/src/follow-up-scheduler.ts:21)

`artifacts/api-server/src/follow-up-scheduler.ts:21` calls `POST https://graph.facebook.com/v22.0/me/messages?access_token=${encodeURIComponent(token)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.fa…

Dangling fetchFetch

`artifacts/api-server/src/routes/fb-inbox.ts:142` calls `POST https://graph.facebook.com/v22.0/me/messages?access_token=${encodeURIComponent(token)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.faceb…

Dangling fetchFetch

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.