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.

snomiao/otoji

https://github.com/snomiao/otoji · scanned 2026-06-16 04:38 UTC (1 month, 3 weeks ago)

7 raw signals (0 security + 7 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 3 weeks ago · v1 · 7 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

55.6% cov · 7 findings

Severity distribution — click a segment to filter

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

Severity: Critical 0 High 0 Medium 4 Low 3 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 7 Crowd 0 Layer: Frontend 1 Security 2 Cicd 2 Quality 2

Exclude dismissed / FP Exclude test files

Scan summary Repository scanned at 88.7/100 with 55.6% coverage. It contains 32 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 7 findings — concentrated in security (2), cicd (2), quality (2). Risk profile is low: 0 critical, 0 high, 4 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

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

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: ci, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts

preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.

package.json CI/CD securitySupply chainNpm

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — main.d.ts:64

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

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/3c3763cb-43a6-4ce1-b2cf-d7db1e268465/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3c3763cb-43a6-4ce1-b2cf-d7db1e268465/

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.