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.

jcode

https://github.com/1jehuang/jcode.git · scanned 2026-05-16 12:49 UTC (1 day, 9 hours ago) · 10 languages

102 findings (14 legacy + 88 scanner) 2/10 scanners ran 40th percentile · Rust · large (100-500K LoC) Scanner says 85 (lower by 15)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week ago · v4 · 100 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
{# ── 2026-05-17 R27 #5: score breakdown panel ────────────────────── Surfaces the score_breakdown JSON that's been silently stored on Repository for months. Turns hidden math into a trust signal. #}
Score breakdown â 2026-05-17-v4 calibration-aware
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 80.4 0.25 20.10
testing_score 36.0 0.20 7.20
documentation_score 86.0 0.15 12.90
practices_score 65.0 0.15 9.75
code_quality 70.0 0.10 7.00
Overall 1.00 69.7
Calibrated penalty buckets (security_score): threat: 19.6
security_score may be inflated — optional scanners skipped due to repo size/fast scan
Severity distribution — click a segment to filter
Active filters: layer: software × excluding tests × Reset all
Severity: Critical 12 High 10 Medium 12 Low 60 Source: Legacy 12 9-layer 88 Crowd 0 Layer: Quality 70 Security 20 Software 8 Api 1 Frontend 1
Scan summary Repository scanned at 84.6/100 with 100.0% coverage. It contains 1723 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 88 findings — concentrated in quality (66), security (15), software (5). Risk profile is high: 12 critical, 0 high, 10 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 8 of 100 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high Legacy software ssrf conf 1.00 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTTP request to a user-controlled URL without allowlist validation. Attackers can probe internal services (169.254.169.254 metadata, internal Kubernetes endpoints, file:// URIs), exfiltrate data, or pivot through your network. SSRF is OWASP A10:2021 and a frequent foothold in cloud breaches.
Validate the URL against an allowlist BEFORE fetching: ALLOWED = {'images.example.com', 'cdn.example.com'} host = urlparse(url).hostname if host not in ALLOWED: abort(400) Or use a server-side proxy (Imgproxy / serve-files-only-from-S3) that isolates outbound network access from the request h…
src/cli/login.rs:43 ssrflegacy
high Legacy software ssrf conf 1.00 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTTP request to a user-controlled URL without allowlist validation. Attackers can probe internal services (169.254.169.254 metadata, internal Kubernetes endpoints, file:// URIs), exfiltrate data, or pivot through your network. SSRF is OWASP A10:2021 and a frequent foothold in cloud breaches.
Validate the URL against an allowlist BEFORE fetching: ALLOWED = {'images.example.com', 'cdn.example.com'} host = urlparse(url).hostname if host not in ALLOWED: abort(400) Or use a server-side proxy (Imgproxy / serve-files-only-from-S3) that isolates outbound network access from the request h…
ios/Sources/JCodeMobile/QRScannerView.swift:95 ssrflegacy
high Legacy software ssrf conf 1.00 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTTP request to a user-controlled URL without allowlist validation. Attackers can probe internal services (169.254.169.254 metadata, internal Kubernetes endpoints, file:// URIs), exfiltrate data, or pivot through your network. SSRF is OWASP A10:2021 and a frequent foothold in cloud breaches.
Validate the URL against an allowlist BEFORE fetching: ALLOWED = {'images.example.com', 'cdn.example.com'} host = urlparse(url).hostname if host not in ALLOWED: abort(400) Or use a server-side proxy (Imgproxy / serve-files-only-from-S3) that isolates outbound network access from the request h…
scripts/oauth_helper.py:39 ssrflegacy
low 9-layer software dead-code-candidate conf 1.00 File has no detected symbols: docs/reddit_dashboard.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
dead-code-candidate
low 9-layer software dead-code conf 1.00 Possibly dead Python function: attributed_total_bytes
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/analyze_runtime_memory_log.py:281 dead-code
low 9-layer software dead-code conf 1.00 Possibly dead Python function: bytes_to_mb
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/analyze_runtime_memory_log.py:246 dead-code
low 9-layer software dead-code conf 1.00 Possibly dead Python function: setup
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/jcode_harbor_agent.py:202 dead-code
info 9-layer software depcruise conf 1.00 dependency-cruiser not installed — JS/TS module graph limited to regex
Repobility's software layer falls back to regex-based JS/TS imports when dependency-cruiser is missing. Install it for a proper module graph (resolves ES6/CommonJS, TS path aliases, dynamic imports): npm install -g dependency-cruiser # binary `depcruise` Override per-project timeout: REPOBILITY…
depcruisetoolingcoverage
{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}
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/02c0aa3c-2fdb-4a26-b86f-531b60354fee/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/02c0aa3c-2fdb-4a26-b86f-531b60354fee/

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.