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

Synergix-lab/WRAI.TH

https://github.com/Synergix-lab/WRAI.TH · scanned 2026-06-16 00:27 UTC (2 months, 2 weeks ago)

39 raw signals (0 security + 39 graph)

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

Complete repo analysis

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

JSON
Combined
62.8
/100
Security checks
63
0 findings
System graph
63
77.8% cov · 39 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 0 Medium 25 Low 9 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 39 Crowd 0 Layer: Frontend 4 Security 16 Cicd 2 Quality 17
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 62.8/100 with 77.8% coverage. It contains 669 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 39 findings — concentrated in quality (17), security (16), frontend (4). Risk profile is low: 0 critical, 0 high, 25 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 34 of 39 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — internal/web/static/js/api-client.js:21
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — internal/web/static/js/notifications.js:236
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — internal/web/static/js/stats.js:258
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — internal/web/static/v2/api.js:4
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 Tests conf 1.00 CI is configured but no tests are detected
A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.
CI/CDConfig theaterRepo hardening
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 cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
golangci/golangci-lint-action@v7 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/lint.yml:20 CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in scripts/team-fullstack.sh:103
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
scripts/team-fullstack.sh:103 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in internal/web/static/js/command-panel.js:612
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
internal/web/static/js/command-panel.js:612 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in internal/web/static/js/kanban.js:631
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
internal/web/static/js/kanban.js:631 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in internal/web/static/js/main.js:745
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
internal/web/static/js/main.js:745 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in internal/web/static/js/notifications.js:160
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
internal/web/static/js/notifications.js:160 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in internal/web/static/js/shortcuts.js:158
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
internal/web/static/js/shortcuts.js:158 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in internal/web/static/js/stats.js:287
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
internal/web/static/js/stats.js:287 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in internal/web/static/v2/board.js:42
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
internal/web/static/v2/board.js:42 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in internal/web/static/v2/home.js:67
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
internal/web/static/v2/home.js:67 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in internal/web/static/v2/linear.js:38
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
internal/web/static/v2/linear.js:38 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in internal/web/static/v2/memory.js:25
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
internal/web/static/v2/memory.js:25 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in internal/web/static/v2/messages.js:92
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
internal/web/static/v2/messages.js:92 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in internal/web/static/v2/notifications.js:24
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
internal/web/static/v2/notifications.js:24 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in internal/web/static/v2/stats.js:20
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
internal/web/static/v2/stats.js:20 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in internal/web/static/v2/team.js:144
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
internal/web/static/v2/team.js:144 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in internal/web/static/v2/v2.js:55
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
internal/web/static/v2/v2.js:55 Direct innerhtml assignment
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 24 placeholder/mock markers across 10 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 Debug conf 1.00 Debug logging residue appears in source files
Found 50 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 — internal/web/static/js/notifications.js:216
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 quality Tests conf 1.00 Low test-to-source ratio
26 tests / 128 src (ratio 0.20).
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 — internal/web/static/js/api-client.js:44
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — internal/web/static/js/main.js:3044
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: internal/relay/api.go (1831 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: internal/web/static/js/main.js (3190 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: internal/web/static/js/space-bg.js (2326 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/4060719f-dd34-41f2-8605-ec1863d8d0da/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/4060719f-dd34-41f2-8605-ec1863d8d0da/

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.