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.

shodaihirofumi-lang/voice-memo

https://github.com/shodaihirofumi-lang/voice-memo · scanned 2026-06-16 00:10 UTC (2 months, 2 weeks ago)

20 raw signals (0 security + 20 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 20 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 20 findings

Severity distribution — click a segment to filter

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

Severity: Critical 0 High 2 Medium 8 Low 7 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 20 Crowd 0 Layer: Frontend 3 Security 2 Cicd 1 Quality 11 Api 3

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 81.9/100 with 77.8% coverage. It contains 166 nodes across 8 cross-layer flows, written primarily in mixed languages. Engine surfaced 20 findings — concentrated in quality (11), frontend (3), api (3). Risk profile is high: 0 critical, 2 high, 8 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 3 of 20 actionable findings. 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.groq.com/openai/v1/audio/transcriptions (server.js:186)

`server.js:186` calls `POST https://api.groq.com/openai/v1/audio/transcriptions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.groq.com/openai/v1/audio/transcriptions` If this points at an external API, …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.todoist.com/api/v1/tasks (server.js:368)

`server.js:368` calls `POST https://api.todoist.com/api/v1/tasks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.todoist.com/api/v1/tasks` If this points at an external API, prefix it with `https://` so t…

Dangling fetchFetch

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

`server.js` declares `GET /api/health` 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/41da9ae7-89aa-4a52-be28-14a64434fb93/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/41da9ae7-89aa-4a52-be28-14a64434fb93/

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.