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

yvesanana-sys/collaboration

https://github.com/yvesanana-sys/collaboration · scanned 2026-06-16 01:10 UTC (2 months, 1 week ago)

87 raw signals (0 security + 87 graph)

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

Complete repo analysis

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

JSON
Combined
72.6
/100
Security checks
73
0 findings
System graph
73
66.7% cov · 81 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 11 Low 61 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 81 Crowd 0 Layer: Software 22 Frontend 1 Security 3 Cicd 2 Quality 30 Api 23
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 72.6/100 with 66.7% coverage. It contains 629 nodes across 24 cross-layer flows, written primarily in mixed languages. Engine surfaced 87 findings — concentrated in quality (35), api (23), software (22). Risk profile is low: 0 critical, 0 high, 11 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 72 of 81 actionable findings. 87 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 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 quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, tests, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
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 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/health-watchdog.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard.html:1024
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard.html:1024 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in strategy_dashboard.html:183
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
strategy_dashboard.html:183 Direct innerhtml assignment
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — bot_with_proxy.py:307
`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 Integrity conf 1.00 Network/subprocess call without timeout or try/except — claude_code_trigger.py:551
`requests.put(...)` 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 Integrity conf 1.00 Network/subprocess call without timeout or try/except — self_repair.py:580
`requests.post(...)` 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 security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 27 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 66 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 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 49, 54
.github/workflows/health-watchdog.yml:49, 54 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 5 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: thesis_manager.py:to_dict, thesis_manager.py:to_dict 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.
5 occurrences
repo-level (5 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: strategy_library_batch2.py:evaluate, strategy_library_batch2.py:evaluate, strategy_library_batch2.py:evaluate This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document w…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: strategy_library.py:evaluate, strategy_library.py:evaluate, strategy_library.py:evaluate, strategy_library.py:evaluate This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or d…
duplicatesduplication
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 quality Docs conf 1.00 No README detected
No README file was found. Generated repos without README context are hard to operate, validate, or safely hand off.
ReadmeRepo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `days_old` in bot_with_proxy.py:3862
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 quality Integrity conf 1.00 Old/deprecated-named symbol `days_old` in market_data.py:746
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 quality Integrity conf 1.00 Old/deprecated-named symbol `days_old` in prompt_builder.py:867
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: activate_strategist
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
strategic_brain.py:874
low System graph software Dead code conf 1.00 Possibly dead Python function: build_ai_prompt_section
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
wallet_intelligence.py:833
low System graph software Dead code conf 1.00 Possibly dead Python function: build_full_wallet_snapshot
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
thesis_manager.py:603
low System graph software Dead code conf 1.00 Possibly dead Python function: build_portfolio_analysis_prompt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
thesis_manager.py:1010
low System graph software Dead code conf 1.00 Possibly dead Python function: build_sleep_brief_prompt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
thesis_manager.py:872
low System graph software Dead code conf 1.00 Possibly dead Python function: build_wake_context
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
thesis_manager.py:521
low System graph software Dead code conf 1.00 Possibly dead Python function: check_all_conditions
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
thesis_manager.py:381
low System graph software Dead code conf 1.00 Possibly dead Python function: check_wake_triggers
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
strategic_brain.py:955
low System graph software Dead code conf 1.00 Possibly dead Python function: clear_thesis
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
thesis_manager.py:768
low System graph software Dead code conf 1.00 Possibly dead Python function: compute_turtle_position_size
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
turtle_math.py:124
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_sleep_brief
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
thesis_manager.py:1074
low System graph software Dead code conf 1.00 Possibly dead Python function: read_full_portfolio
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
wallet_intelligence.py:354
low System graph software Dead code conf 1.00 Possibly dead Python function: reset_session
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
self_repair.py:896
low System graph software Dead code conf 1.00 Possibly dead Python function: reset_triggered_session
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
thesis_manager.py:773
low System graph software Dead code conf 1.00 Possibly dead Python function: scan_log_line
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
self_repair.py:421
low System graph software Dead code conf 1.00 Possibly dead Python function: set_account
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboard_strategies.py:59
low System graph software Dead code conf 1.00 Possibly dead Python function: shadow_endpoint
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
committee_shadow.py:138
low System graph software Dead code conf 1.00 Possibly dead Python function: start_shadow_thread
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
committee_shadow.py:126
low System graph software Dead code conf 1.00 Possibly dead Python function: trigger_claude_code_repair
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
claude_code_trigger.py:302
low System graph software Dead code conf 1.00 Possibly dead Python function: trigger_scheduled_maintenance
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
claude_code_trigger.py:429
low System graph software Dead code conf 1.00 Possibly dead Python function: update_from_sleep_brief
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
thesis_manager.py:236
low System graph software Dead code conf 1.00 Possibly dead Python function: update_repair_log_attempt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
claude_code_trigger.py:207
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 api Wiring conf 1.00 Unused endpoint: ANY /api/strategies
`dashboard_strategies.py` declares `ANY /api/strategies` 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: ANY /binance_history
`bot_with_proxy.py` declares `ANY /binance_history` 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: ANY /core_reserve
`bot_with_proxy.py` declares `ANY /core_reserve` 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: ANY /crypto_status
`bot_with_proxy.py` declares `ANY /crypto_status` 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: ANY /dashboard
`bot_with_proxy.py` declares `ANY /dashboard` 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: ANY /dashboard.html
`bot_with_proxy.py` declares `ANY /dashboard.html` 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: ANY /deploy
`bot_with_proxy.py` declares `ANY /deploy` 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: ANY /evolution
`bot_with_proxy.py` declares `ANY /evolution` 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: ANY /history
`bot_with_proxy.py` declares `ANY /history` 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: ANY /leaderboard
`bot_with_proxy.py` declares `ANY /leaderboard` 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: ANY /liquidate
`bot_with_proxy.py` declares `ANY /liquidate` 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: ANY /memory
`bot_with_proxy.py` declares `ANY /memory` 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: ANY /pdt
`bot_with_proxy.py` declares `ANY /pdt` 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: ANY /performance
`bot_with_proxy.py` declares `ANY /performance` 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: ANY /projection
`bot_with_proxy.py` declares `ANY /projection` 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: ANY /prompt_memory
`bot_with_proxy.py` declares `ANY /prompt_memory` 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: ANY /repair_log
`bot_with_proxy.py` declares `ANY /repair_log` 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: ANY /repair_status
`bot_with_proxy.py` declares `ANY /repair_status` 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: ANY /stats
`bot_with_proxy.py` declares `ANY /stats` 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: ANY /storage
`bot_with_proxy.py` declares `ANY /storage` 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: ANY /strategies
`dashboard_strategies.py` declares `ANY /strategies` 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: ANY /strategy
`bot_with_proxy.py` declares `ANY /strategy` 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: ANY /strategy/<ai_name>
`bot_with_proxy.py` declares `ANY /strategy/<ai_name>` 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 quality Complexity conf 1.00 Very large file: binance_crypto.py (4350 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: bot_with_proxy.py (4902 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core_reserve.py (1277 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: prompt_builder.py (1329 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: thesis_manager.py (1162 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/4a0a49d7-e52c-4480-983c-72c5fd507c4a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/4a0a49d7-e52c-4480-983c-72c5fd507c4a/

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.