qixing-jk/all-api-hub

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/qixing-jk/all-api-hub · scanned 2026-05-31 01:22 UTC (5 days, 14 hours ago) · 10 languages

557 findings (89 legacy + 468 scanner) 11/13 scanners ran 66th percentile · Typescript · medium (20-100K LoC) Scanner says 71 (higher by 6)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 14 hours ago · v2 · last Δ +1.0 (diff) · 330 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 · 241 gaps

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	100.0	0.25	25.00
`testing_score`	47.0	0.20	9.40
`documentation_score`	83.0	0.15	12.45
`practices_score`	65.0	0.15	9.75
`code_quality`	75.0	0.10	7.50
Overall		1.00	76.8

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: layer: hardware × excluding tests × Reset all

Severity: Critical 20 High 48 Medium 37 Low 154 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 89 9-layer 241 Crowd 0 Layer: Quality 93 Security 27 Software 85 Api 1 Frontend 55 Hardware 3 Cicd 66

Exclude dismissed / FP Exclude test files

Scan summary Repository scanned at 70.8/100 with 100.0% coverage. It contains 8558 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 241 findings — concentrated in cicd (66), frontend (55), software (53). Risk profile is high: 16 critical, 0 high, 31 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

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

medium 9-layer hardware security conf 1.00 Dockerfile runs as root: docs_assistant/Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

securitycontainer

low 9-layer hardware coverage conf 1.00 Containers defined but no K8s/orchestration manifest found

Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.

coveragedeployment

low 9-layer hardware supply-chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.9-slim

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

docs_assistant/Dockerfile:1 supply-chaindockerpinned-dependencies

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/521a15e0-f936-43c2-a40a-9973995ae905/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/521a15e0-f936-43c2-a40a-9973995ae905/

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.