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.

soyesenna/specraft

https://github.com/soyesenna/specraft · scanned 2026-06-16 00:19 UTC (2 months, 2 weeks ago)

106 raw signals (0 security + 106 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: layer: api × excluding tests × Reset all

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

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 54.2/100 with 100.0% coverage. It contains 4721 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 106 findings — concentrated in security (37), quality (36), api (17). Risk profile is high: 2 critical, 1 high, 53 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 17 of 98 actionable findings. 106 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: POST https://api.anthropic.com/v1/messages/count_tokens (scripts/measure-tool-tokens.mjs:45)

`scripts/measure-tool-tokens.mjs:45` calls `POST https://api.anthropic.com/v1/messages/count_tokens` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages/count_tokens` If this points a…

Dangling fetchFetch

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/keys

`apps/backend/src/auth/routes.ts` declares `DELETE /api/v1/keys` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/admin/invites

`apps/backend/src/auth/routes.ts` declares `GET /api/v1/admin/invites` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/admin/members

`apps/backend/src/auth/routes.ts` declares `GET /api/v1/admin/members` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/admin/settings

`apps/backend/src/auth/routes.ts` declares `GET /api/v1/admin/settings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/auth/session

`apps/backend/src/auth/routes.ts` declares `GET /api/v1/auth/session` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/keys

`apps/backend/src/auth/routes.ts` declares `GET /api/v1/keys` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/admin/git/test-connection

`apps/backend/src/auth/routes.ts` declares `POST /api/v1/admin/git/test-connection` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/admin/invites

`apps/backend/src/auth/routes.ts` declares `POST /api/v1/admin/invites` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/admin/members/enable

`apps/backend/src/auth/routes.ts` declares `POST /api/v1/admin/members/enable` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/auth/bootstrap-admin

`apps/backend/src/auth/routes.ts` declares `POST /api/v1/auth/bootstrap-admin` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/auth/login

`apps/backend/src/auth/routes.ts` declares `POST /api/v1/auth/login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/auth/logout

`apps/backend/src/auth/routes.ts` declares `POST /api/v1/auth/logout` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/auth/signup

`apps/backend/src/auth/routes.ts` declares `POST /api/v1/auth/signup` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/keys

`apps/backend/src/auth/routes.ts` declares `POST /api/v1/keys` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/v1/admin/members/:id/disable

`apps/backend/src/auth/routes.ts` declares `PUT /api/v1/admin/members/:id/disable` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/v1/admin/settings

`apps/backend/src/auth/routes.ts` declares `PUT /api/v1/admin/settings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

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/75939c86-6411-4083-8469-d1dae0ab8367/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/75939c86-6411-4083-8469-d1dae0ab8367/

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.