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.

RazonIn4K/shopmatch-pro

https://github.com/RazonIn4K/shopmatch-pro · scanned 2026-06-16 04:36 UTC (1 month, 3 weeks ago)

13 raw signals (0 security + 13 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 3 weeks ago · v1 · 12 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

77.8% cov · 12 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 1 Medium 4 Low 3 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 12 Crowd 0 Layer: Frontend 2 Security 4 Quality 6

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 67.5/100 with 77.8% coverage. It contains 58 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 13 findings — concentrated in quality (6), security (5), frontend (2). Risk profile is high: 4 critical, 1 high, 4 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 10 of 12 actionable findings. 13 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 .env.local.example

Detected pattern matching private_key. Rotate the credential and move to a secret manager.

.env.local.example:60

critical System graph security Secrets conf 1.00 Possible secret in .env.local.template

Detected pattern matching private_key. Rotate the credential and move to a secret manager.

.env.local.template:60

high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: CLAUDE.md

Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.

CLAUDE.md:452 SecretsClaude instruction

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — jest.setup.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 Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing

AI-coder instruction files were found, but the repo is missing tests. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.

Repo hardeningGenerated repo pattern

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

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 37 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 Tests conf 1.00 Low test-to-source ratio

1 tests / 10 src (ratio 0.10).

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — test-firestore-rules.js:36

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/c80e1ccc-46d5-4db0-a883-8fcaa226fce7/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c80e1ccc-46d5-4db0-a883-8fcaa226fce7/

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.