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.

spacedock-dev/spacedock

https://github.com/spacedock-dev/spacedock · scanned 2026-06-16 00:19 UTC (2 months, 2 weeks ago)

31 raw signals (0 security + 31 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Severity distribution — click a segment to filter
Active filters: severity: low × excluding tests × Reset all
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 60.8/100 with 66.7% coverage. It contains 649 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 31 findings — concentrated in cicd (19), quality (9), data (1). Risk profile is low: 0 critical, 0 high, 15 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

Showing 2 of 15 actionable findings. 31 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 System graph cicd CI/CD security conf 1.00 13 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
4 files, 13 locations
.github/workflows/release.yml:29, 34, 103, 111, 132, 144 (6 hits)
.github/workflows/runtime-live-e2e.yml:208, 329, 436 (3 hits)
.github/workflows/docs.yml:31, 34 (2 hits)
.github/workflows/next-publish.yml:19, 22 (2 hits)
CI/CD securitySupply chainGithub actions
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/7df984b5-e7a6-45b9-9994-b042cd2bf86a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7df984b5-e7a6-45b9-9994-b042cd2bf86a/

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.