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.
Sign up free Scan another repo

tdsmaxinsano/map-hub

https://github.com/tdsmaxinsano/map-hub · scanned 2026-06-16 04:39 UTC (1 month, 3 weeks ago)

22 raw signals (0 security + 22 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
59.4
/100
Security checks
59
0 findings
System graph
59
55.6% cov · 22 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 2 Medium 15 Low 5 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 22 Crowd 0 Layer: Frontend 1 Security 12 Quality 9
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 59.4/100 with 55.6% coverage. It contains 90 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 22 findings — concentrated in security (12), quality (9), frontend (1). Risk profile is high: 0 critical, 2 high, 15 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 22 of 22 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 security security conf 1.00 Insecure pattern 'eval_used' in CLAUDE.md:175
Found a known-risky pattern (eval_used). Review and replace if possible.
CLAUDE.md:175 Eval used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in supabase.js:1
Found a known-risky pattern (new_function_used). Review and replace if possible.
supabase.js:1 New function used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — supabase.js:1
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci, tests, operator-readme. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in agencies.html:466
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
agencies.html:466 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in chat-widget.js:334
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
chat-widget.js:334 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in compliance.html:1334
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
compliance.html:1334 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in finance.html:2307
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
finance.html:2307 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in index.html:1021
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
index.html:1021 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in kanban.html:1054
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
kanban.html:1054 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in referrals.html:733
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
referrals.html:733 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in roster-review.html:1059
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
roster-review.html:1059 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in time-tracker.html:995
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
time-tracker.html:995 Direct innerhtml assignment
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 3 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 7 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph security security conf 1.00 Insecure pattern 'document_write' in finance.html:6221
Found a known-risky pattern (document_write). Review and replace if possible.
finance.html:6221 Document write
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Docs conf 1.00 No README detected
No README file was found. Generated repos without README context are hard to operate, validate, or safely hand off.
ReadmeRepo hardeningGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase.js:1
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
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/f377203f-5ee4-497f-a4e8-42f787e0ccf5/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f377203f-5ee4-497f-a4e8-42f787e0ccf5/

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.