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.

admin-vazgro/Vazgroagency

https://github.com/admin-vazgro/Vazgroagency · scanned 2026-06-17 01:29 UTC (1 month, 2 weeks ago)

81 raw signals (0 security + 81 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ +4.1 (diff) · 81 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 81 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 0 Medium 9 Low 9 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 81 Crowd 0 Layer: Api 1 Frontend 47 Security 3 Quality 30

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

Showing 20 of 81 actionable findings. 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 e2e/helpers.ts

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

e2e/helpers.ts:3

critical System graph security Secrets conf 1.00 Possible secret in e2e/seed.mjs

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

e2e/seed.mjs:21

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — app/blog/markdown.tsx:7

Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html

Fq dangerous html

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — components/seo/JsonLd.tsx:9

Fq dangerous html

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — components/geo/CurrencyProvider.tsx: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 quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — components/services/LaunchExperience.tsx:433

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 Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: license, ci, 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 'dangerous_innerhtml' in components/seo/JsonLd.tsx:9

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

components/seo/JsonLd.tsx:9 Dangerous innerhtml

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 189 placeholder/mock markers across 52 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

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

1 test file(s) for 309 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Integrity conf 1.00 5 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `E2E_BASE_URL`, `NEXT_PUBLIC_SITE_URL`, `NODE_ENV`, `SUPABASE_ACCESS_TOKEN`, `SUPABASE_PROJECT_REF`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.

config drift

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

Found 10 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 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 quality Integrity conf 1.00 Old/deprecated-named symbol `vz_geo_v1` in components/geo/CurrencyProvider.tsx:37

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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — app/api/webhooks/stripe/route.ts:352

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: app/api/webhooks/stripe/route.ts (1867 lines)

Files with >800 lines often hide complexity hotspots and discourage tests.

low System graph quality Complexity conf 1.00 Very large file: lib/database.types.ts (3353 lines)

Files with >800 lines often hide complexity hotspots and discourage tests.

low System graph quality Complexity conf 1.00 Very large file: lib/landing/solution-finder.ts (1664 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/215650d8-443d-4c5a-a42b-2266861db672/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/215650d8-443d-4c5a-a42b-2266861db672/

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.