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.

petwashglobal/petwash-marketplace

https://github.com/petwashglobal/petwash-marketplace · scanned 2026-06-16 02:56 UTC (2 months, 1 week ago)

160 raw signals (145 security + 15 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 14 findings

Severity distribution — click a segment to filter

Active filters: severity: low × excluding tests × Reset all

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

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 86.3/100 with 100.0% coverage. It contains 55 nodes across 3 cross-layer flows, written primarily in mixed languages. Engine surfaced 15 findings — concentrated in quality (8), hardware (3), frontend (1). Risk profile is low: 0 critical, 0 high, 3 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 6 of 22 actionable findings. 316 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.

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: `CI`, `DATABASE_URL`, `NODE_ENV`, `PORT`, `REPLIT_DEV_DOMAIN`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.

config drift

low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found

Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.

Deployment

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

Found 8 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 hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: node:22-slim

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

lines 14, 43

Dockerfile:14, 43 (2 hits)

containersPinned dependencies

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 api Wiring conf 1.00 Unused endpoint: GET /

`server.cjs` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

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/b3682c09-af21-49ce-9101-324448fc6e15/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b3682c09-af21-49ce-9101-324448fc6e15/

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.