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

xvanov/software-factory

https://github.com/xvanov/software-factory · scanned 2026-06-16 01:04 UTC (2 months, 1 week ago)

84 raw signals (0 security + 84 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. 3 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
58.8
/100
Security checks
59
0 findings
System graph
59
100.0% 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 26 Low 19 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 81 Crowd 0 Layer: Software 4 Network 14 Frontend 1 Security 5 Cicd 2 Quality 54 Api 1
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 58.8/100 with 100.0% coverage. It contains 2692 nodes across 2 cross-layer flows, written primarily in mixed languages. Engine surfaced 84 findings — concentrated in quality (56), network (14), security (5). Risk profile is low: 0 critical, 0 high, 26 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 43 of 81 actionable findings. 84 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 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. 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 security security conf 1.00 Insecure pattern 'subprocess_shell_true' in factory/chain/gates/evaluator.py:105
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
factory/chain/gates/evaluator.py:105 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in factory/chain/scheduled_tasks.py:156
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
factory/chain/scheduled_tasks.py:156 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in factory/deploy/runner.py:125
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
factory/deploy/runner.py:125 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in factory/manager/circuit_breaker.py:247
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
factory/manager/circuit_breaker.py:247 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in factory/runner.py:648
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
factory/runner.py:648 Subprocess shell true
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — factory/chain/handlers.py:2584
`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
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — factory/chain/rollback.py:161
`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
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — factory/manager/circuit_breaker.py:324
`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
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 60 placeholder/mock markers across 16 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 13 in use
Port 13 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
apps/sacrifice/directions/012-align-chat-affordances-with-current-implementation/state.yaml Ports
medium System graph network Security conf 1.00 Privileged port 15 in use
Port 15 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
apps/sacrifice/directions/014-reduce-dead-end-states-in-goal-type-selection/state.yaml Ports
medium System graph network Security conf 1.00 Privileged port 16 in use
Port 16 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
apps/factory/directions/001-factory-management-system/state.yaml Ports
medium System graph network Security conf 1.00 Privileged port 17 in use
Port 17 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
apps/sacrifice/directions/005-bootstrap-context/state.yaml Ports
medium System graph network Security conf 1.00 Privileged port 18 in use
Port 18 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
apps/sacrifice/directions/009-chat-goal-creation/state.yaml Ports
medium System graph network Security conf 1.00 Privileged port 20 in use
Port 20 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
apps/sacrifice/directions/004-vague-thought/state.yaml Ports
medium System graph network Security conf 1.00 Privileged port 23 in use
Port 23 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
apps/sacrifice/directions/009-chat-goal-creation/state.yaml Ports
medium System graph network Security conf 1.00 Privileged port 24 in use
Port 24 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
apps/sacrifice/directions/009-chat-goal-creation/state.yaml Ports
medium System graph network Security conf 1.00 Privileged port 26 in use
Port 26 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
apps/sacrifice/directions/002-add-healthz-endpoint/state.yaml Ports
medium System graph network Security conf 1.00 Privileged port 30 in use
Port 30 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
apps/sacrifice/directions/005-bootstrap-context/state.yaml Ports
medium System graph network Security conf 1.00 Privileged port 32 in use
Port 32 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
apps/sacrifice/directions/004-vague-thought/state.yaml Ports
medium System graph network Security conf 1.00 Privileged port 33 in use
Port 33 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
apps/sacrifice/directions/004-vague-thought/state.yaml Ports
medium System graph network Security conf 1.00 Privileged port 34 in use
Port 34 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
apps/sacrifice/directions/004-vague-thought/state.yaml Ports
medium System graph network Security conf 1.00 Privileged port 40 in use
Port 40 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
apps/sacrifice/directions/005-bootstrap-context/state.yaml Ports
low System graph quality Integrity conf 1.00 10 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AZURE_AI_API_BASE`, `AZURE_AI_API_VERSION`, `AZURE_API_BASE`, `EDITOR`, `FACTORY_PROVIDER`, `FACTORY_SANDBOX_TIMEOUT_S`, `FACTORY_SHARD`, `FACTORY_STATE_ROOT` + 2 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't br…
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 96 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 3 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: factory/chain/worktree.py:ensure_worktree_for_story, factory/chain/worktree.py:remove_worktree_for_story 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 th…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: factory/chain/ux_auditor.py:ux_auditor_tick, factory/chain/bug_hunter.py:bug_hunter_tick, factory/chain/security.py:security_tick This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Conso…
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: factory/manager/self_context.py:text_run, factory/manager/summarizer.py:text_run, factory/manager/diagnostician.py:text_run, factory/manager/watcher.py:text_run This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https:…
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 8 places
Functions with the same first-5-line body hash: factory/chain/handlers.py:handle_sm, factory/chain/handlers.py:handle_dev, factory/chain/handlers.py:handle_review, factory/chain/handlers.py:handle_tech_writer This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https:…
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 Integrity conf 1.00 Old/deprecated-named symbol `t_very_old` in tests/manager/test_watcher.py:320
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 `too_old` in tests/manager/detectors/test_placeholder_prompts.py:54
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: action_recompute_baselines
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
factory/tui/app.py:408
low System graph software Dead code conf 1.00 Possibly dead Python function: bump_cursor
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
factory/directions/watcher.py:120
low System graph software Dead code conf 1.00 Possibly dead Python function: compose
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
factory/tui/app.py:379
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_slug
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
factory/directions/parser.py:295
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: POST /webhook/github
`factory/webhook/github.py` declares `POST /webhook/github` 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: factory/chain/handlers.py (2822 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: factory/cli.py (2900 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: factory/runner.py (1600 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/9d303a35-7ef1-487f-83ad-c9afc3014dd7/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/9d303a35-7ef1-487f-83ad-c9afc3014dd7/

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.