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

blainomd/co-op-care-vercel

https://github.com/blainomd/co-op-care-vercel · scanned 2026-06-16 02:52 UTC (2 months, 1 week ago)

23 raw signals (0 security + 23 graph)

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

Complete repo analysis

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

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

Showing 21 of 23 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 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 auth.js:163
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
auth.js:163 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in boulder.html:575
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
boulder.html:575 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in calculator.html:691
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
calculator.html:691 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in crm.html:360
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
crm.html:360 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in feedback.html:133
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
feedback.html:133 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in footer-cta.js:34
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
footer-cta.js:34 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in found.html:704
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
found.html:704 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in hearth.html:849
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
hearth.html:849 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in join.html:845
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
join.html:845 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in m.html:381
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
m.html:381 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in marketplace.html:849
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
marketplace.html:849 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in nav.js:97
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
nav.js:97 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in profile.html:825
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
profile.html:825 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in why.html:2106
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
why.html:2106 Direct innerhtml assignment
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
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 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 — auth.js:39
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/1f11e4e6-383f-4e47-8bb6-61ab5d1393bd/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/1f11e4e6-383f-4e47-8bb6-61ab5d1393bd/

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.