SnailDev/douyin-hot-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.

2 of your 4 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Upstream (GitHub) caused delay on this scan — not Repobility.

GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
Clone from GitHub took 252.48s for a 1362.7 MB repo slow.
Repobility's analysis ran in 8.49s after the clone landed.

https://github.com/SnailDev/douyin-hot-hub · scanned 2026-06-05 18:49 UTC (4 days, 17 hours ago) · 10 languages

3 findings 11/13 scanners ran 87th percentile · Python · tiny (<2K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

2 actionable findings from 1 signal source. 1 repeated signal grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	40.0	0.15	6.00
`security_score`	100.0	0.25	25.00
`testing_score`	70.0	0.20	14.00
`documentation_score`	80.0	0.15	12.00
`practices_score`	72.0	0.15	10.80
`code_quality`	69.0	0.10	6.90
Overall		1.00	74.7

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 0 High 0 Medium 0 Low 2 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 2 System graph 0 Crowd 0 Layer: Quality 1 Cicd 1

Exclude dismissed / FP Exclude test files

Showing 2 of 2 actionable findings. 3 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

low Security checks cicd CI/CD security conf 0.90 ✓ Repobility 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned

[MINED115] Action `actions/checkout` pinned to mutable ref `@v2`: `uses: actions/checkout@v2` resolves at workflow-run time. Tags and branches can be re-pushed by the action owner; that made the tj-actions/changed-files compromise (2025) instantly affect ~23K repos. Pin to a 40-char commit SHA + lo…

lines 17, 21

.github/workflows/schedule.yml:17, 21 (2 hits)

CI/CD securitySupply chainGitHub Actions

low Security checks quality Quality conf 0.68 Archive or legacy directory is mixed into the active repository root

Move archived code out of the active repository, mark it with .repobilityignore, or document exactly why it must stay and how scanners should treat it.

archives:1

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/2ae8e6c5-7ea1-4be9-ae2e-9edff1589ac8/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2ae8e6c5-7ea1-4be9-ae2e-9edff1589ac8/

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.