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.

SnailDev/v2ex-hot-hub

https://github.com/SnailDev/v2ex-hot-hub · scanned 2026-06-16 00:17 UTC (2 months, 2 weeks ago)

20 raw signals (0 security + 20 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 17 actionable findings from 1 signal source. 3 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 17 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

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

Showing 15 of 17 actionable findings. 20 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.

critical System graph security Secrets conf 1.00 2 occurrences Possible secret in raw/2023-05-22.json

Detected pattern matching openai_or_anthropic_key. Rotate the credential and move to a secret manager.

lines 1

raw/2023-05-22.json:1 (2 hits)

critical System graph security Secrets conf 1.00 2 occurrences Possible secret in raw/2026-02-06.json

Detected pattern matching openai_or_anthropic_key. Rotate the credential and move to a secret manager.

lines 1

raw/2026-02-06.json:1 (2 hits)

high System graph security security conf 1.00 Insecure pattern 'eval_used' in raw/2022-03-30.json:1

Found a known-risky pattern (eval_used). Review and replace if possible.

raw/2022-03-30.json:1 Eval used

medium System graph quality Tests conf 1.00 CI is configured but no tests are detected

A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.

CI/CDConfig theaterRepo hardening

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in raw/2021-08-09.json:1

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

raw/2021-08-09.json:1 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in raw/2022-10-10.json:1

Found a known-risky pattern (weak_hash). Review and replace if possible.

raw/2022-10-10.json:1 Weak hash

medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in raw/2023-11-08.json:1

Found a known-risky pattern (weak_hash). Review and replace if possible.

raw/2023-11-08.json:1 Weak hash

medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in raw/2025-04-12.json:1

Found a known-risky pattern (weak_hash). Review and replace if possible.

raw/2025-04-12.json:1 Weak hash

medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in raw/2025-08-16.json:1

Found a known-risky pattern (weak_hash). Review and replace if possible.

raw/2025-08-16.json:1 Weak hash

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

0 test file(s) for 3 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

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

Multiple low-cost hardening controls are missing together: tests, operator-readme. 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 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned

actions/checkout@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

lines 19, 23

.github/workflows/schedule-update.yml:19, 23 (2 hits)

CI/CD securitySupply chainGithub actions

low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places

Functions with the same first-5-line body hash: main.py:topic, main.py:topic This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.

duplicatesduplication

low System graph quality Docs conf 1.00 README lacks setup or run instructions

A README exists, but it does not contain common install/setup/run markers. This matches a frequent generated-code pattern: UI is present, operational handoff is thin.

ReadmeRepo hardeningGenerated repo pattern

low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence

The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.

Git historyGenerated repo pattern

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/068024ab-75df-4570-ac2c-b490f3ca872a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/068024ab-75df-4570-ac2c-b490f3ca872a/

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.