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

RichardEko/mycelium

https://github.com/RichardEko/mycelium · scanned 2026-06-15 23:51 UTC (2 months, 3 weeks ago)

59 raw signals (0 security + 59 graph)

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

Complete repo analysis

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

JSON
Combined
70.4
/100
Security checks
70
0 findings
System graph
70
88.9% cov · 54 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 0 Medium 14 Low 38 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 54 Crowd 0 Layer: Software 16 Frontend 3 Network 1 Hardware 12 Cicd 2 Quality 20
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 70.4/100 with 88.9% coverage. It contains 603 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 59 findings — concentrated in quality (23), software (16), hardware (14). Risk profile is low: 0 critical, 0 high, 14 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 52 of 54 actionable findings. 59 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.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — mycelium-ts/src/agent.ts:549
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 — mycelium-ts/src/prompt_skill.ts:126
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 — mycelium-ts/src/sse.ts:16
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 — mycelium-ts/src/tuple.ts:106
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 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 hardware Security conf 1.00 Dockerfile runs as root: docker/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: docker/llm-agent-runner/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: docker/three-node-runner/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: examples/fluid_pipeline/coordinator/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: examples/fluid_pipeline/worker/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
contributor-assistant/[email protected] can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/cla.yml:27 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/cla.yml CI/CD securitySupply chainGithub actions
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 53 placeholder/mock markers across 9 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 network Security conf 1.00 Privileged port 6 in use
Port 6 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/ci.yml Ports
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 55 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 Docker base image is tag-pinned but not digest-pinned: alpine:3.19
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
docker/llm-agent-runner/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: alpine:3.19
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
docker/three-node-runner/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: debian:bookworm-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
docker/Dockerfile:29 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
examples/fluid_pipeline/coordinator/Dockerfile:15 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
examples/fluid_pipeline/worker/Dockerfile:15 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 3 occurrences Docker base image is tag-pinned but not digest-pinned: rust:1.88-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
3 files, 3 locations
docker/Dockerfile:2
examples/fluid_pipeline/coordinator/Dockerfile:2
examples/fluid_pipeline/worker/Dockerfile:2
containersPinned dependencies
low System graph quality Tests conf 1.00 Low test-to-source ratio
15 tests / 102 src (ratio 0.15).
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: examples/fluid_pipeline/coordinator/coordinator.py:wait_ready, examples/fluid_pipeline/worker/worker.py:wait_ready This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or docum…
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph software Dead code conf 1.00 Possibly dead Python function: aggregate_article
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
examples/fluid_pipeline/worker/stages/aggregate.py:16
low System graph software Dead code conf 1.00 Possibly dead Python function: call
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
mycelium-py/src/mycelium/prompt_skill.py:147
low System graph software Dead code conf 1.00 Possibly dead Python function: cross_group_propose
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
mycelium-py/src/mycelium/agent.py:715
low System graph software Dead code conf 1.00 Possibly dead Python function: delete_prompt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
mycelium-py/src/mycelium/prompt_skill.py:134
low System graph software Dead code conf 1.00 Possibly dead Python function: distributed_lock
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
mycelium-py/src/mycelium/agent.py:686
low System graph software Dead code conf 1.00 Possibly dead Python function: do_POST
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
examples/community/mock_llm.py:69
low System graph software Dead code conf 1.00 Possibly dead Python function: emit_reliable
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
mycelium-py/src/mycelium/agent.py:824
low System graph software Dead code conf 1.00 Possibly dead Python function: emit_sharded
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
mycelium-py/src/mycelium/agent.py:861
low System graph software Dead code conf 1.00 Possibly dead Python function: enrich_article
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
examples/fluid_pipeline/worker/stages/enrich.py:34
low System graph software Dead code conf 1.00 Possibly dead Python function: log_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
examples/community/mock_llm.py:58
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_article
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
examples/fluid_pipeline/worker/stages/parse.py:8
low System graph software Dead code conf 1.00 Possibly dead Python function: score_article
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
examples/fluid_pipeline/worker/stages/score.py:23
low System graph software Dead code conf 1.00 Possibly dead Python function: set_with_min_acks
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
mycelium-py/src/mycelium/agent.py:458
low System graph software Dead code conf 1.00 Possibly dead Python function: shard_for
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
mycelium-py/src/mycelium/agent.py:849
low System graph software Dead code conf 1.00 Possibly dead Python function: subscribe_log
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
mycelium-py/src/mycelium/agent.py:779
low System graph software Dead code conf 1.00 Possibly dead Python function: update_prompt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
mycelium-py/src/mycelium/prompt_skill.py:120
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 — mycelium-ts/src/a2a.ts:13
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 — mycelium-ts/src/prompt_skill.ts:22
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: examples/llm_agent.rs (2015 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: examples/mesh_demo.rs (1683 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: examples/three_node_demo.rs (1782 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: mycelium-core/src/config.rs (1277 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: mycelium-core/src/store.rs (1122 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: mycelium-tuple-space/src/store.rs (1803 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/agent/http.rs (2997 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/consensus.rs (1601 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/lib_tests.rs (3509 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/0cb10be8-70d5-44b8-a26c-3f6e102c6625/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0cb10be8-70d5-44b8-a26c-3f6e102c6625/

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.