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

relyon360mfrc/relyon360

https://github.com/relyon360mfrc/relyon360 · scanned 2026-06-15 23:49 UTC (2 months, 3 weeks ago)

57 raw signals (0 security + 57 graph)

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

Complete repo analysis

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

JSON
Combined
77.5
/100
Security checks
78
0 findings
System graph
78
77.8% cov · 56 findings
Critical
1
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 1 High 0 Medium 5 Low 28 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 56 Crowd 0 Layer: Frontend 3 Security 9 Cicd 1 Quality 43
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 77.5/100 with 77.8% coverage. It contains 847 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 57 findings — concentrated in quality (43), security (9), frontend (3). Risk profile is high: 1 critical, 0 high, 5 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 33 of 56 actionable findings. 57 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.

critical System graph security Secrets conf 1.00 Possible secret in js/constants.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
js/constants.js:10
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — sw.js:89
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 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 'cors_wildcard' in supabase/functions/login/index.ts:27
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/login/index.ts:27 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in js/app.js:61
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
js/app.js:61 Local storage auth token
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 115 placeholder/mock markers across 16 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 30 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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — js/schedule.js:1124
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph security security conf 1.00 Insecure pattern 'document_write' in js/coverage.js:92
Found a known-risky pattern (document_write). Review and replace if possible.
js/coverage.js:92 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in js/dashboard.js:853
Found a known-risky pattern (document_write). Review and replace if possible.
js/dashboard.js:853 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in js/instructors.js:1164
Found a known-risky pattern (document_write). Review and replace if possible.
js/instructors.js:1164 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in js/poolbatch.js:197
Found a known-risky pattern (document_write). Review and replace if possible.
js/poolbatch.js:197 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in js/reports.js:129
Found a known-risky pattern (document_write). Review and replace if possible.
js/reports.js:129 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in js/schedule.js:1343
Found a known-risky pattern (document_write). Review and replace if possible.
js/schedule.js:1343 Document write
low System graph quality Tests conf 1.00 Low test-to-source ratio
4 tests / 37 src (ratio 0.11).
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 quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — agents/mcp/src/index.ts:19
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
low System graph quality Complexity conf 1.00 Very large file: js/admin.js (885 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: js/ai.js (1198 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: js/app.js (886 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: js/communication.js (981 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: js/config.js (1570 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: js/coverage.js (1046 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: js/dashboard.js (1563 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: js/instructor.js (1065 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: js/instructors.js (1418 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: js/poolbatch.js (1190 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: js/reports.js (3082 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: js/schedule.js (2321 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: js/trainings.js (1203 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/7c3568df-df81-4566-b4b2-88889679aada/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/7c3568df-df81-4566-b4b2-88889679aada/

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.