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, 7 hours ago) · 10 languages

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

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 7 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: 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

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

Possible secret in src/features/ImportExport/searchTargets.ts

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in src/features/ImportExport/searchTargets.ts:5; move to env var / secrets manager.

src/features/ImportExport/searchTargets.ts:5

Possible secret in src/features/ImportExport/searchTargets.ts

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in src/features/ImportExport/searchTargets.ts:14; move to env var / secrets manager.

src/features/ImportExport/searchTargets.ts:14

`dangerouslySetInnerHTML` used in a React component — src/features/SiteAnnouncements/AnnouncementMarkdown.tsx:71

GapSeverity.MEDIUM Layer.FRONTEND score 0.360

Why: medium severity

Insecure pattern 'cors_wildcard' in src/locales/ja/settings.json:85

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

src/locales/ja/settings.json:85

Insecure pattern 'cors_wildcard' in src/locales/en/settings.json:85

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

src/locales/en/settings.json:85

Insecure pattern 'dangerous_innerhtml' in src/features/SiteAnnouncements/AnnouncementMarkdown.tsx:71

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

src/features/SiteAnnouncements/AnnouncementMarkdown.tsx:71

GitHub Action is tag-pinned rather than SHA-pinned

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/e2e-real-site.yml:46

GitHub Action is tag-pinned rather than SHA-pinned

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/test.yml:50

GitHub Action is tag-pinned rather than SHA-pinned

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/test.yml:88

#10

GitHub Action is tag-pinned rather than SHA-pinned

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/test.yml:107

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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.