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.

Vieeeeeee/pocket-wardrobe

https://github.com/Vieeeeeee/pocket-wardrobe · scanned 2026-06-16 00:49 UTC (2 months, 1 week ago)

27 raw signals (0 security + 27 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 25 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 14 Low 7 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 25 Crowd 0 Layer: Frontend 2 Security 10 Cicd 1 Quality 12

Exclude dismissed / FP Exclude test files

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 75.7/100 with 77.8% coverage. It contains 313 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 27 findings — concentrated in quality (12), security (10), cicd (3). Risk profile is low: 0 critical, 0 high, 14 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 21 of 25 actionable findings. 27 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.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — functions/api/_google.js:19

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 — functions/api/_tryon-shared.js:566

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 — functions/api/tryon-listenhub.js:131

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 — functions/api/tryon.js:67

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 security security conf 1.00 Insecure pattern 'cors_wildcard' in functions/api/_tryon-shared.js:604

Found a known-risky pattern (cors_wildcard). Review and replace if possible.

functions/api/_tryon-shared.js:604 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in functions/api/classify.js:184

Found a known-risky pattern (cors_wildcard). Review and replace if possible.

functions/api/classify.js:184 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in functions/api/img/[key].js:19

Found a known-risky pattern (cors_wildcard). Review and replace if possible.

functions/api/img/[key].js:19 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in functions/api/inspire.js:275

Found a known-risky pattern (cors_wildcard). Review and replace if possible.

functions/api/inspire.js:275 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin.html:326

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

admin.html:326 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in index.html:6561

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

index.html:6561 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in index.html:8081

Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.

index.html:8081 Direct outerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in index.html:7493

Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.

index.html:7493 Insert adjacent html

medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in index.html:6745

Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.

index.html:6745 Local storage auth token

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

1 test file(s) for 39 source file(s) (ratio 0.03). 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 6 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 cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned

actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

lines 15, 18, 28

.github/workflows/d1-backup.yml:15, 18, 28 (3 hits)

CI/CD securitySupply chainGithub actions

low System graph security security conf 1.00 Insecure pattern 'document_write' in index.html:13778

Found a known-risky pattern (document_write). Review and replace if possible.

index.html:13778 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 Integrity conf 1.00 Old/deprecated-named symbol `pw_pending_combo_v1` in tests/regression/critical-flows.spec.mjs:119

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

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 — functions/api/_log.js:30

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/548b0fdc-0eaa-4a87-9139-0b631fb4f2d3/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/548b0fdc-0eaa-4a87-9139-0b631fb4f2d3/

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.