openhuman

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.

https://github.com/tinyhumansai/openhuman · scanned 2026-05-17 19:50 UTC (35 minutes ago) · 10 languages

1415 findings (74 legacy + 1341 scanner) 8/10 scanners ran Scanner says 79 (lower by 18)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 35 minutes ago · v3 · last Δ -0.1 (diff) · 525 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

100.0% cov · 451 gaps

{# ── 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`	21.5	0.25	5.38
`testing_score`	81.0	0.20	16.20
`documentation_score`	75.0	0.15	11.25
`practices_score`	75.0	0.15	11.25
`code_quality`	43.0	0.10	4.30
Overall		1.00	61.1

Calibrated penalty buckets (security_score): agent: 8.1 Â· authz: 4.6 Â· docker: 15.3 Â· threat: 37.0 Â· journey: 13.5

Severity distribution — click a segment to filter

Active filters: severity: critical × excluding tests × Reset all

Scan summary Repository scanned at 78.8/100 with 100.0% coverage. It contains 5808 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 451 findings — concentrated in quality (164), cicd (147), frontend (79). Risk profile is high: 0 critical, 3 high, 86 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

critical Legacy security credential_exposure conf 1.00 [SEC019] Raw Authorization Token in Example: A real-looking API token appears in an Authorization-style header or service-key example. Use placeholders in docs and CI snippets; never paste live tokens into source, comments, or README files.

Replace the value with a placeholder, revoke or rotate the exposed token, and store live values only in a masked secret store.

src/openhuman/memory/tree/jobs/redact.rs:137 credential_exposurelegacy

Replace the value with a placeholder, revoke or rotate the exposed token, and store live values only in a masked secret store.

src/openhuman/memory/safety/mod.rs:351 credential_exposurelegacy

{# ── 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/fc621168-a7ef-4013-b97a-0b4d573d408e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/fc621168-a7ef-4013-b97a-0b4d573d408e/

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.