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

1jehuang/jcode

https://github.com/1jehuang/jcode · scanned 2026-07-23 19:42 UTC (1 month, 2 weeks ago)

196 raw signals (0 security + 196 graph)

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

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v7 · 193 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
70.6
/100
Security checks
71
0 findings
System graph
71
80.0% cov · 193 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: severity: medium × excluding tests × Reset all
Severity: Critical 0 High 4 Medium 38 Low 151 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 193 Crowd 0 Layer: Software 19 Security 17 Cicd 4 Quality 140 Dependencies 13
Scan summary Repository scanned at 70.6/100 with 80.0% coverage. It contains 3428 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 196 findings — concentrated in quality (140), software (19), security (17). Risk profile is high: 0 critical, 4 high, 40 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 33 of 193 actionable findings. 196 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 lockfile. 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 Trivy conf 1.00 CVE-2026-50185: cmov 0.5.3 — Cargo.lock
RustCrypto CMOV provides conditional move CPU intrinsics which are gua ... RustCrypto CMOV provides conditional move CPU intrinsics which are guaranteed on major platforms to execute in constant-time and not be rewritten as branches by the compiler. From 0.1.1 until 0.5.4, the aarch64 implementati…
VulnCve 2026 50185
medium System graph security Trivy conf 1.00 CVE-2026-55093: tract-nnef 0.21.10 — Cargo.lock
tract-nnef: integer overflow in NNEF `.dat` tensor parser yields an out-of-bounds read on model load - **Component:** `tract-nnef` (`nnef/src/tensors.rs::read_tensor`) + `tract-data` (`data/src/tensor.rs`) - **Affected versions:** `< 0.21.16`, `0.22.0`–`0.22.2`, `0.23.0`–`0.23.1` — the dense `DatL…
VulnCve 2026 55093
medium System graph security Trivy conf 1.00 CVE-2026-55832: tract-onnx 0.21.10 — Cargo.lock
tract: Arbitrary file read via unsanitized ONNX external_data `location` (path traversal) on model load in tract-onnx ### Summary `tract` (the `tract-onnx` crate) resolves an ONNX tensor's external-data `location` by joining it onto the model directory **without any sanitization**. Because `locat…
VulnCve 2026 55832
medium System graph security Semgrep conf 0.55 dynamic urllib use detected — scripts/post_discord_release.py:75
Detected a dynamic value being used with urllib. urllib supports 'file://' schemes, so a dynamic value controlled by a malicious actor may allow them to read arbitrary files. Audit uses of urllib calls to ensure user data cannot control the URLs, or consider using the 'requests' library instead. R…
scripts/post_discord_release.py:75 SecurityPython
medium System graph security Trivy conf 1.00 GHSA-3pv8-6f4r-ffg2: tar 0.4.45 — Cargo.lock
tar has a PAX header desynchronization issue ### Summary When a tar stream contains multiple "header" entries prior to a file entry, tar-rs applies the PAX header (`x`) to the _next_ entry in the stream, regardless of type. For example, a stream of `x -> L -> file` (PAX, GNU longname, file) would…
VulnGhsa 3pv8 6f4r ffg2
medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
webfactory/[email protected] can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 3 locations
.github/workflows/ci.yml:29
.github/workflows/freebsd-smoke.yml:41
.github/workflows/release.yml:94
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/discord-release.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 security security conf 1.00 Insecure pattern 'cors_wildcard' in crates/jcode-base/src/gateway.rs:328
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
crates/jcode-base/src/gateway.rs:328 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in scripts/phone-server/wake-lambda.py:122
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
scripts/phone-server/wake-lambda.py:122 Local storage auth token
medium System graph quality Integrity conf 0.85 Network/subprocess call without timeout or try/except — scripts/bench_memory_cli.py:69
`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.
scripts/bench_memory_cli.py:69 runtime safetyRobustness
medium System graph quality Integrity conf 0.85 Network/subprocess call without timeout or try/except — scripts/bench_startup.py:101
`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.
scripts/bench_startup.py:101 runtime safetyRobustness
medium System graph quality Integrity conf 0.85 Network/subprocess call without timeout or try/except — scripts/bench_startup_visible_ready.py:81
`subprocess.check_output(...)` 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.
scripts/bench_startup_visible_ready.py:81 runtime safetyRobustness
medium System graph quality Integrity conf 0.85 Network/subprocess call without timeout or try/except — scripts/benchmark_swarm.py:109
`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.
scripts/benchmark_swarm.py:109 runtime safetyRobustness
medium System graph quality Integrity conf 0.85 Network/subprocess call without timeout or try/except — scripts/check_dependency_boundaries.py:55
`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.
scripts/check_dependency_boundaries.py:55 runtime safetyRobustness
medium System graph quality Integrity conf 0.85 Network/subprocess call without timeout or try/except — scripts/compare_token_usage.py:79
`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.
scripts/compare_token_usage.py:79 runtime safetyRobustness
medium System graph quality Integrity conf 0.85 Network/subprocess call without timeout or try/except — scripts/compile_isolation_report.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.
scripts/compile_isolation_report.py:44 runtime safetyRobustness
medium System graph quality Integrity conf 0.85 Network/subprocess call without timeout or try/except — scripts/oauth_helper.py:39
`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.
scripts/oauth_helper.py:39 runtime safetyRobustness
medium System graph quality Integrity conf 0.85 Network/subprocess call without timeout or try/except — scripts/profile_spawn.py:580
`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.
scripts/profile_spawn.py:580 runtime safetyRobustness
medium System graph quality Integrity conf 0.85 Network/subprocess call without timeout or try/except — scripts/run_terminal_bench_campaign.py:21
`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.
scripts/run_terminal_bench_campaign.py:21 runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 453 placeholder/mock markers across 107 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 security Trivy conf 1.00 Secret leak: JWT token — crates/jcode-app-core/src/tool/discover.rs
Trivy detected a possible secret in `crates/jcode-app-core/src/tool/discover.rs`. Rule: jwt-token Severity: MEDIUM Match (redacted): "Use *************************************************************** Action: rotate the credential and remove it from the repo. Use a secrets manager or…
Secret
medium System graph dependencies dependencies conf 1.00 Vulnerable dependency anyhow 1.0.100: RUSTSEC-2026-0190
OSV.dev reports `anyhow` at version `1.0.100` (resolved in `Cargo.lock`) is affected by RUSTSEC-2026-0190. Unsoundness in `Error::downcast_mut()` Advisory: https://osv.dev/vulnerability/RUSTSEC-2026-0190 Fix: upgrade `anyhow` past the affected range per the advisory.
Cargo.toml ScaOsvRustsec 2026 0190
medium System graph dependencies dependencies conf 0.90 Vulnerable dependency bincode 1.3.3: RUSTSEC-2025-0141
OSV.dev reports `bincode` at version `1.3.3` (resolved in `Cargo.lock`) is affected by RUSTSEC-2025-0141. Note: `bincode` is a transitive dependency — pulled in by another package, not declared directly in a manifest. Bincode is unmaintained Advisory: https://osv.dev/vulnerability/RUSTSEC-2025-01…
Cargo.lock ScaOsvRustsec 2025 0141
medium System graph dependencies dependencies conf 0.90 Vulnerable dependency cmov 0.5.3: GHSA-3rjw-m598-pq24
OSV.dev reports `cmov` at version `0.5.3` (resolved in `Cargo.lock`) is affected by GHSA-3rjw-m598-pq24 (aka CVE-2026-50185). Note: `cmov` is a transitive dependency — pulled in by another package, not declared directly in a manifest. Cmov/CmovEq on aarch64 can produce wrong results if high-bits o…
Cargo.lock ScaOsvGhsa 3rjw m598 pq24
medium System graph dependencies dependencies conf 0.90 Vulnerable dependency lru 0.12.5: GHSA-rhfx-m35p-ff5j
OSV.dev reports `lru` at version `0.12.5` (resolved in `Cargo.lock`) is affected by GHSA-rhfx-m35p-ff5j. Note: `lru` is a transitive dependency — pulled in by another package, not declared directly in a manifest. `IterMut` violates Stacked Borrows by invalidating internal pointer Aliases: GHSA-rh…
Cargo.lock ScaOsvGhsa rhfx m35p ff5j
medium System graph dependencies dependencies conf 0.90 Vulnerable dependency memmap2 0.8.0: RUSTSEC-2026-0186
OSV.dev reports `memmap2` at version `0.8.0` (resolved in `Cargo.lock`) is affected by RUSTSEC-2026-0186. Note: `memmap2` is a transitive dependency — pulled in by another package, not declared directly in a manifest. Unchecked pointer offset in crate `memmap2` Advisory: https://osv.dev/vulnerabi…
Cargo.lock ScaOsvRustsec 2026 0186
medium System graph dependencies dependencies conf 0.90 Vulnerable dependency memmap2 0.9.9: RUSTSEC-2026-0186
OSV.dev reports `memmap2` at version `0.9.9` (resolved in `Cargo.lock`) is affected by RUSTSEC-2026-0186. Note: `memmap2` is a transitive dependency — pulled in by another package, not declared directly in a manifest. Unchecked pointer offset in crate `memmap2` Advisory: https://osv.dev/vulnerabi…
Cargo.lock ScaOsvRustsec 2026 0186
medium System graph dependencies dependencies conf 1.00 Vulnerable dependency rand 0.8.5: GHSA-cq8v-f236-94qc
OSV.dev reports `rand` at version `0.8.5` (resolved in `Cargo.lock`) is affected by GHSA-cq8v-f236-94qc. Rand is unsound with a custom logger using rand::rng() Aliases: GHSA-cq8v-f236-94qc, RUSTSEC-2026-0097 Advisory: https://osv.dev/vulnerability/GHSA-cq8v-f236-94qc Fix: upgrade `rand` past the …
Cargo.lock ScaOsvGhsa cq8v f236 94qc
medium System graph dependencies dependencies conf 1.00 Vulnerable dependency tar 0.4.45: GHSA-3pv8-6f4r-ffg2
OSV.dev reports `tar` at version `0.4.45` (resolved in `Cargo.lock`) is affected by GHSA-3pv8-6f4r-ffg2. tar has a PAX header desynchronization issue Advisory: https://osv.dev/vulnerability/GHSA-3pv8-6f4r-ffg2 Fix: upgrade `tar` past the affected range per the advisory.
crates/jcode-app-core/Cargo.toml ScaOsvGhsa 3pv8 6f4r ffg2
medium System graph dependencies dependencies conf 1.00 Vulnerable dependency tract-onnx 0.21.10: GHSA-h668-6x6g-f8r5
OSV.dev reports `tract-onnx` at version `0.21.10` (resolved in `Cargo.lock`) is affected by GHSA-h668-6x6g-f8r5 (aka CVE-2026-55832). tract: Arbitrary file read via unsanitized ONNX external_data `location` (path traversal) on model load in tract-onnx Aliases: CVE-2026-55832 Advisory: https://osv…
crates/jcode-embedding/Cargo.toml ScaOsvGhsa h668 6x6g f8r5
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/8ae5b755-b1c9-453b-9aeb-119088507671/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/8ae5b755-b1c9-453b-9aeb-119088507671/

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.