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.
Sign up free Scan another repo

renatmannanov/wndrverse

https://github.com/renatmannanov/wndrverse · scanned 2026-06-15 23:49 UTC (2 months, 3 weeks ago)

20 raw signals (0 security + 20 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
87.0
/100
Security checks
87
0 findings
System graph
87
88.9% cov · 20 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 2 Medium 3 Low 9 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 20 Crowd 0 Layer: Software 4 Hardware 1 Frontend 1 Cicd 1 Quality 13
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 87.0/100 with 88.9% coverage. It contains 620 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 20 findings — concentrated in quality (13), software (4), hardware (1). Risk profile is high: 0 critical, 2 high, 3 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 14 of 20 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph quality Integrity conf 1.00 Blocking `httpx.get(...)` inside `async def check_github` — agent-template/agent_cron.py:40
Sync I/O inside an async function blocks the event loop. While `httpx.get(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asyncio.to_threa…
agent-template/agent_cron.py:40 Sync io in asyncPerformance
high System graph quality Integrity conf 1.00 Blocking `httpx.get(...)` inside `async def check_tg_channel` — agent-template/agent_cron.py:69
Sync I/O inside an async function blocks the event loop. While `httpx.get(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asyncio.to_threa…
agent-template/agent_cron.py:69 Sync io in asyncPerformance
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 ci. 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 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 cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
low System graph quality Integrity conf 1.00 16 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AGENT_MASHA_TOKEN`, `AGENT_ONE_BOT_TOKEN`, `AGENT_RENAT_TOKEN`, `AGENT_VASYA_TOKEN`, `ANTHROPIC_API_KEY`, `BOT_TOKEN`, `BUS_CHAT_ID`, `CURATOR_BOT_TOKEN` + 8 more. 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 38 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 Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: delivery/cli.py:repl, delivery/cli.py:repl This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
duplicatesduplication
low System graph software Dead code conf 1.00 Possibly dead Python function: insert_fragment
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/store/fragments_db.py:106
low System graph software Dead code conf 1.00 Possibly dead Python function: repl
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
delivery/cli.py:122
low System graph software Dead code conf 1.00 Possibly dead Python function: run_clustering
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/brain/clustering.py:80
low System graph software Dead code conf 1.00 Possibly dead Python function: search_by_embedding
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/store/fragments_db.py:303
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
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/f41b3c3b-1106-477c-b47a-6152f41e527d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f41b3c3b-1106-477c-b47a-6152f41e527d/

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.