moinulmoin/voicetypr

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.

48 of your 187 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.7s · analysis 37.97s · 3.7 MB · GitHub API rate-limit (preflight)

https://github.com/moinulmoin/voicetypr · scanned 2026-06-06 00:11 UTC (4 days, 3 hours ago) · 10 languages

362 raw signals (170 security + 192 graph) 49th percentile · Typescript · medium (20-100K LoC) System graph score 62 (higher by 6)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 3 hours ago · v2 · 187 actionable findings from 2 signal sources. 79 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 58 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	33.1	0.25	8.28
`testing_score`	92.0	0.20	18.40
`documentation_score`	71.7	0.15	10.76
`practices_score`	80.0	0.15	12.00
`code_quality`	64.8	0.10	6.48
Overall		1.00	68.7

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 5 High 61 Medium 28 Low 66 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 129 System graph 58 Crowd 0 Layer: Quality 21 Security 12 Software 129 Cicd 4 Api 1 Frontend 20

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 1 finding

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/`.

1 matching finding on this repo

info Commented-code block (7 lines) in src/components/ShareStatsModal.tsx:154

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 File has no detected symbols: vite.config.ts
low File has no detected symbols: vitest.config.ts

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/5e454e6b-e586-479d-8a08-5e6782d8c705/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5e454e6b-e586-479d-8a08-5e6782d8c705/

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.