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

yusong652/yade-mcp

https://github.com/yusong652/yade-mcp · scanned 2026-06-16 01:09 UTC (2 months, 1 week ago)

44 raw signals (0 security + 44 graph)

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

Complete repo analysis

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

JSON
Combined
52.2
/100
Security checks
52
0 findings
System graph
52
77.8% cov · 41 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 4 Medium 4 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 41 Crowd 0 Layer: Software 13 Hardware 3 Frontend 1 Security 4 Cicd 2 Quality 18
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 52.2/100 with 77.8% coverage. It contains 1394 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 44 findings — concentrated in quality (21), software (13), security (4). Risk profile is high: 0 critical, 4 high, 4 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 28 of 41 actionable findings. 44 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 security security conf 1.00 Insecure pattern 'eval_used' in yade-mcp-bridge/src/yade_mcp_bridge/execution/script.py:76
Found a known-risky pattern (eval_used). Review and replace if possible.
yade-mcp-bridge/src/yade_mcp_bridge/execution/script.py:76 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in yade-mcp-bridge/src/yade_mcp_bridge/handlers/execute_code.py:311
Found a known-risky pattern (eval_used). Review and replace if possible.
yade-mcp-bridge/src/yade_mcp_bridge/handlers/execute_code.py:311 Eval used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in yade-mcp-bridge/src/yade_mcp_bridge/execution/script.py:79
Found a known-risky pattern (exec_used). Review and replace if possible.
yade-mcp-bridge/src/yade_mcp_bridge/execution/script.py:79 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in yade-mcp-bridge/src/yade_mcp_bridge/handlers/execute_code.py:314
Found a known-risky pattern (exec_used). Review and replace if possible.
yade-mcp-bridge/src/yade_mcp_bridge/handlers/execute_code.py:314 Exec used
medium System graph hardware Security conf 1.00 Dockerfile runs as root: 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 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/release-bridge.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/release.yml CI/CD securitySupply chainGithub actions
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/restructure_docs.py:169
`subprocess.run(...)` 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
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 33 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: 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.
Dockerfile:1 containersPinned dependencies
low System graph quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
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: yade-mcp-bridge/src/yade_mcp_bridge/utils/file_buffer.py:write, yade-mcp-bridge/src/yade_mcp_bridge/utils/file_buffer.py:write This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolid…
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_build_returns_copy` in tests/bridge/test_utils.py:88
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 software Dead code conf 1.00 Possibly dead Python function: checkConsolidation
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
showcase/triaxial/triaxial_consolidation.py:91
low System graph software Dead code conf 1.00 Possibly dead Python function: checkReequilib
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
showcase/triaxial/triaxial_reequilibrate.py:10
low System graph software Dead code conf 1.00 Possibly dead Python function: do_GET
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
yade-mcp-bridge/src/yade_mcp_bridge/transport/server.py:178
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.
yade-mcp-bridge/src/yade_mcp_bridge/transport/server.py:100
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.
yade-mcp-bridge/src/yade_mcp_bridge/transport/server.py:74
low System graph software Dead code conf 1.00 Possibly dead Python function: normalize_input
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/yade_mcp/utils.py:31
low System graph software Dead code conf 1.00 Possibly dead Python function: readable
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
yade-mcp-bridge/src/yade_mcp_bridge/console/capture.py:40
low System graph software Dead code conf 1.00 Possibly dead Python function: recordData
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
showcase/triaxial/triaxial_drained_shear.py:55
low System graph software Dead code conf 1.00 Possibly dead Python function: run_server_background
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
yade-mcp-bridge/src/yade_mcp_bridge/bootstrap.py:97
low System graph software Dead code conf 1.00 Possibly dead Python function: seekable
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
yade-mcp-bridge/src/yade_mcp_bridge/console/capture.py:46
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_script_path
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/yade_mcp/utils.py:47
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_task_description
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/yade_mcp/utils.py:55
low System graph software Dead code conf 1.00 Possibly dead Python function: writable
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
yade-mcp-bridge/src/yade_mcp_bridge/console/capture.py:43
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/ab52e284-2cbe-4307-8b44-0e4287753b9d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ab52e284-2cbe-4307-8b44-0e4287753b9d/

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.