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.

snoowood/stone_server

https://github.com/snoowood/stone_server · scanned 2026-06-16 04:39 UTC (1 month, 3 weeks ago)

7 raw signals (0 security + 7 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 3 weeks ago · v1 · 7 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 7 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 0 Medium 2 Low 4 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 7 Crowd 0 Layer: Hardware 2 Security 2 Cicd 1 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 75.2/100 with 77.8% coverage. It contains 31 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 7 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 7 of 7 actionable findings. 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 .env.example

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

.env.example:24

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard.html:445

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

dashboard.html:445 Direct innerhtml assignment

medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected

No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.

CI/CD securityCoverage

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

Multiple low-cost hardening controls are missing together: license, ci. 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: alpine:3.19

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

Dockerfile:14 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: golang:1.25-alpine

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

Dockerfile:1 containersPinned dependencies

low System graph quality License conf 1.00 No license file detected

No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.

Repo hardeningGenerated 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/bde9c1f2-d44c-4028-900f-9219205d6400/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/bde9c1f2-d44c-4028-900f-9219205d6400/

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.