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

soliblue/cloude

https://github.com/soliblue/cloude · scanned 2026-06-16 00:17 UTC (2 months, 2 weeks ago)

48 raw signals (0 security + 48 graph)

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

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 46 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
Combined
64.0
/100
Security checks
64
0 findings
System graph
64
88.9% cov · 46 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 7 Medium 20 Low 17 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 46 Crowd 0 Layer: Software 1 Frontend 5 Security 11 Cicd 3 Quality 19 Api 7
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 64.0/100 with 88.9% coverage. It contains 1785 nodes across 7 cross-layer flows, written primarily in mixed languages. Engine surfaced 48 findings — concentrated in quality (19), security (11), api (7). Risk profile is high: 0 critical, 7 high, 20 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 40 of 46 actionable findings. 48 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.

high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/${REPO}/releases?per_page=20 (daemons/linux/src/Updater/DaemonUpdater.js:63)
`daemons/linux/src/Updater/DaemonUpdater.js:63` calls `GET https://api.github.com/repos/${REPO}/releases?per_page=20` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/repos/<p>/releases` If this …
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI DELETE `delete_tunnel` without auth dependency — provisioning/app/api/macs.py:62
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
provisioning/app/api/macs.py:62 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `complete_pairing_session` without auth dependency — provisioning/app/api/pairing_sessions.py:57
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
provisioning/app/api/pairing_sessions.py:57 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_pairing_session` without auth dependency — provisioning/app/api/pairing_sessions.py:22
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
provisioning/app/api/pairing_sessions.py:22 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `put_heartbeat` without auth dependency — provisioning/app/api/macs.py:78
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
provisioning/app/api/macs.py:78 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `put_mac` without auth dependency — provisioning/app/api/macs.py:18
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
provisioning/app/api/macs.py:18 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `put_tunnel` without auth dependency — provisioning/app/api/macs.py:33
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
provisioning/app/api/macs.py:33 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — daemons/linux/src/Provisioning/RemoteTunnelClient.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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — daemons/linux/src/Updater/DaemonUpdater.js:63
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 authority lacks a verifier contract: .claude/plans/1_next/streaming-robustness-audit.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/plans/1_next/streaming-robustness-audit.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/consult/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/consult/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/sim/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/sim/SKILL.md VerificationClaude instruction
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 license, 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 cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/mac-agent.yml CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/linux-agent.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in daemons/linux/src/Handlers/GitHandler.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
daemons/linux/src/Handlers/GitHandler.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in daemons/linux/src/Handlers/SessionHandler.js:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
daemons/linux/src/Handlers/SessionHandler.js:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in daemons/linux/src/Handlers/TranscribeHandler.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
daemons/linux/src/Handlers/TranscribeHandler.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in daemons/linux/src/Runner.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
daemons/linux/src/Runner.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in daemons/linux/src/Updater/DaemonUpdater.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
daemons/linux/src/Updater/DaemonUpdater.js:1 Node child process
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — .github/scripts/asc_certs.py:47
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 52 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 7 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CLOUDE_DATA`, `CLOUDE_DISPLAY_NAME`, `CLOUDE_HOST`, `CLOUDE_PORT`, `CLOUDE_PROVISIONING_URL`, `HOME`, `PATH`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 28 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/setup-node@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 3 locations
.github/workflows/linux-agent.yml:29, 62 (2 hits)
.github/workflows/mac-agent.yml:72
CI/CD securitySupply chainGithub actions
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 software Dead code conf 1.00 Possibly dead Python function: dependency
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
provisioning/app/core/rate_limit.py:15
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 — daemons/linux/index.js:11
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — daemons/linux/scripts/provision.js:37
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — daemons/linux/src/Networking/HTTPServer.js:44
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — daemons/linux/src/Updater/DaemonUpdater.js:17
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 api Wiring conf 1.00 Unused endpoint: DELETE /tunnel
`provisioning/app/api/macs.py` declares `DELETE /tunnel` 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
low System graph api Wiring conf 1.00 Unused endpoint: POST /
`provisioning/app/api/pairing_sessions.py` declares `POST /` 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
low System graph api Wiring conf 1.00 Unused endpoint: POST /{pairing_id}/completion
`provisioning/app/api/pairing_sessions.py` declares `POST /{pairing_id}/completion` 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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /
`provisioning/app/api/macs.py` declares `PUT /` 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
low System graph api Wiring conf 1.00 Unused endpoint: PUT /heartbeat
`provisioning/app/api/macs.py` declares `PUT /heartbeat` 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
low System graph api Wiring conf 1.00 Unused endpoint: PUT /tunnel
`provisioning/app/api/macs.py` declares `PUT /tunnel` 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/6fe0da1b-fa35-40c7-bee7-b6622c3bddf9/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/6fe0da1b-fa35-40c7-bee7-b6622c3bddf9/

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.