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.

gizmax/Sandcastle

https://github.com/gizmax/Sandcastle · scanned 2026-06-16 04:25 UTC (2 months ago)

6 raw signals (0 security + 6 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months ago · v1 · 5 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.

JSON

77.8% cov · 5 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

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

Showing 5 of 5 actionable findings. 6 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 Possible secret in docker-compose.yml

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

docker-compose.yml:52

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — build_docker_image.py:26

`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph security Coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.

auth

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 20 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.

CleanupRepo hardeningGenerated repo pattern

low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.12-slim

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

lines 2, 20

Dockerfile:2, 20 (2 hits)

containersPinned dependencies

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/d179b84f-0337-4d32-a336-9be5cbf77890/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d179b84f-0337-4d32-a336-9be5cbf77890/

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.