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.

7t1-studio/cloud71-mcp

https://github.com/7t1-studio/cloud71-mcp · scanned 2026-06-17 01:11 UTC (1 month, 2 weeks ago)

4 raw signals (0 security + 4 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ +16.9 (diff) · 4 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

66.7% cov · 4 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

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 93.6/100 with 66.7% coverage. It contains 59 nodes across 3 cross-layer flows, written primarily in mixed languages. Engine surfaced 4 findings — concentrated in quality (3), cicd (1). Risk profile is low: 0 critical, 0 high, 4 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/cloud71.ts:65

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

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 cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned

cloudflare/wrangler-action@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

.github/workflows/ci.yml:39 CI/CD securitySupply chainGithub actions

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

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

Coverage

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/2ac4879d-0333-4411-a7ff-7ed1e911b42b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2ac4879d-0333-4411-a7ff-7ed1e911b42b/

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.