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.

massonflorian89-lab/wineblender-3-demo

https://github.com/massonflorian89-lab/wineblender-3-demo · scanned 2026-06-16 04:33 UTC (1 month, 4 weeks ago)

49 raw signals (0 security + 49 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
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 92.8/100 with 55.6% coverage. It contains 418 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 49 findings — concentrated in security (31), quality (16), frontend (2). Risk profile is low: 0 critical, 0 high, 34 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 40 of 49 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. 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 analyses.html:814
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
analyses.html:814 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in apports.html:448
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
apports.html:448 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in assemblage.html:121
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
assemblage.html:121 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in compare.js:54
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
compare.js:54 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in contenant-detail.html:287
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
contenant-detail.html:287 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in cuverie-tournee.js:147
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
cuverie-tournee.js:147 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in cuverie.html:1757
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
cuverie.html:1757 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard.html:468
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard.html:468 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in db.js:234
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
db.js:234 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in list-date-filter.js:120
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
list-date-filter.js:120 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in list-header.js:88
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
list-header.js:88 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in list-pager.js:104
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
list-pager.js:104 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in lot-detail.html:565
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
lot-detail.html:565 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in lots.html:452
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
lots.html:452 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in multiselect-touch.js:56
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
multiselect-touch.js:56 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in nav.js:152
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
nav.js:152 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in operations.html:559
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
operations.html:559 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in parametres.html:258
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
parametres.html:258 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in planning.html:449
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
planning.html:449 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in produits.html:384
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
produits.html:384 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pwa.js:95
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pwa.js:95 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in qualite-traca.html:271
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
qualite-traca.html:271 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in rapports.html:340
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
rapports.html:340 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in row-popover.js:92
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
row-popover.js:92 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in shell.html:543
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
shell.html:543 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in toast.js:68
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
toast.js:68 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in tracabilite.html:387
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
tracabilite.html:387 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in wb3-freshness.js:75
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
wb3-freshness.js:75 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in wb3-vitals.js:99
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
wb3-vitals.js:99 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in apports.html:1395
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
apports.html:1395 Insert adjacent html
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 23 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 16 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 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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — auth.js:73
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 — wb3-vitals.js:75
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: db.js (3154 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: nav.js (1157 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/2b1fbf73-b813-494c-9fa0-0ca7a0039aed/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2b1fbf73-b813-494c-9fa0-0ca7a0039aed/

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.