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

teamchong/pxpipe

https://github.com/teamchong/pxpipe · scanned 2026-06-16 00:30 UTC (2 months, 2 weeks ago)

64 raw signals (0 security + 64 graph)

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

Complete repo analysis

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

JSON
Combined
69.2
/100
Security checks
69
0 findings
System graph
69
88.9% cov · 57 findings
Critical
2
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 2 High 3 Medium 16 Low 18 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 57 Crowd 0 Layer: Software 5 Frontend 6 Security 14 Cicd 1 Quality 31
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 69.2/100 with 88.9% coverage. It contains 699 nodes across 3 cross-layer flows, written primarily in mixed languages. Engine surfaced 64 findings — concentrated in quality (34), security (15), software (8). Risk profile is high: 3 critical, 3 high, 16 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 39 of 57 actionable findings. 64 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.

critical System graph security security conf 1.00 Insecure pattern 'private_key_in_repo' in eval/corpus/sessions.json:78
Found a known-risky pattern (private_key_in_repo). Review and replace if possible.
eval/corpus/sessions.json:78 Private key in repo
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in eval/corpus/sessions.json
Detected pattern matching private_key. Rotate the credential and move to a secret manager.
lines 78
eval/corpus/sessions.json:78 (2 hits)
high System graph security security conf 1.00 Insecure pattern 'eval_used' in eval/README.md:23
Found a known-risky pattern (eval_used). Review and replace if possible.
eval/README.md:23 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in README.md:28
Found a known-risky pattern (eval_used). Review and replace if possible.
README.md:28 Eval used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in src/dashboard/vendor.ts:5
Found a known-risky pattern (new_function_used). Review and replace if possible.
src/dashboard/vendor.ts:5 New function used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/vendor-ui.mjs:17
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 — src/worker.ts:47
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 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 security security conf 1.00 Insecure pattern 'cors_wildcard' in src/dashboard.ts:884
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
src/dashboard.ts:884 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/dashboard/vendor.ts:5
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/dashboard/vendor.ts:5 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in src/dashboard/vendor.ts:5
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
src/dashboard/vendor.ts:5 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in eval/lib/anthropic-client.mjs:33
Found a known-risky pattern (node_child_process). Review and replace if possible.
eval/lib/anthropic-client.mjs:33 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in eval/run-eval.mjs:28
Found a known-risky pattern (node_child_process). Review and replace if possible.
eval/run-eval.mjs:28 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/build.mjs:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/build.mjs:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in eval/swe-bench-pro/rep_nav.py:44
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
eval/swe-bench-pro/rep_nav.py:44 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in eval/swe-bench-pro/run_pro.py:53
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
eval/swe-bench-pro/run_pro.py:53 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in eval/swe-bench/run_pilot.py:28
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
eval/swe-bench/run_pilot.py:28 Subprocess shell true
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — eval/swe-bench-pro/rep_nav.py:44
`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 — eval/swe-bench-pro/run_pro.py:53
`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 — eval/swe-bench/run_pilot.py:28
`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 quality Debug conf 1.00 Debug logging residue appears in source files
Found 138 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 4 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: eval/gist-recall/run3.py:ask, eval/gist-recall/run2.py:ask, eval/gist-recall/run.py:ask 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.
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `uptime_sec_unused` in src/dashboard/types.ts:52
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 4 occurrences Possibly dead Python function: one
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
4 files, 4 locations
eval/gist-recall/run.py:20
eval/gist-recall/run2.py:20
eval/gist-recall/run3.py:20
eval/gsm8k/bench.py:33
low System graph software Dead code conf 1.00 Possibly dead Python function: t_diff
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
eval/gsm8k/gen_novel.py:20
low System graph software Dead code conf 1.00 Possibly dead Python function: t_muladd
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
eval/gsm8k/gen_novel.py:16
low System graph software Dead code conf 1.00 Possibly dead Python function: t_subadd
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
eval/gsm8k/gen_novel.py:12
low System graph software Dead code conf 1.00 Possibly dead Python function: t_sum3
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
eval/gsm8k/gen_novel.py:8
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 — scripts/gen-atlas.ts:134
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 — src/core/tracker.ts:373
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 — src/dashboard/vendor.ts:5
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 — src/node.ts:82
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 — src/worker.ts:71
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 — tests/reflow.test.ts:473
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: src/core/transform.ts (2698 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/dashboard.ts (1111 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/render.test.ts (2299 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/35b97c1b-66e9-4818-bef9-3001e3d6e289/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/35b97c1b-66e9-4818-bef9-3001e3d6e289/

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.