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.
Sign up free Scan another repo

thaynes43/haynes-ops

https://github.com/thaynes43/haynes-ops · scanned 2026-06-16 00:33 UTC (2 months, 2 weeks ago)

33 raw signals (0 security + 33 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 32 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
Combined
75.1
/100
Security checks
75
0 findings
System graph
75
88.9% cov · 32 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 0 Medium 25 Low 5 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 32 Crowd 0 Layer: Network 18 Hardware 2 Frontend 1 Cicd 4 Quality 7
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.1/100 with 88.9% coverage. It contains 1882 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 33 findings — concentrated in network (18), quality (7), cicd (5). Risk profile is low: 0 critical, 0 high, 26 medium. Recommended next step: open the network layer findings first — that's where the highest-impact wins live.

Showing 30 of 32 actionable findings. 33 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.

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing tests. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
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 hardware Security conf 1.00 Dockerfile runs as root: scripts/peloton-scrape/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
docker/login-action@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 23, 30
.github/workflows/peloton-scraper-build.yml:23, 30 (2 hits)
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/publishmkdocs.yml CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/peloton-scraper-build.yml CI/CD securitySupply chainGithub actions
medium System graph network Security conf 1.00 Privileged port 1000 in use
Port 1000 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
kubernetes/main/apps/ai/stable-diffusion/comfyui/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 1001 in use
Port 1001 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
archive/alumni/scripts/bootstrap-vm.sh Ports
medium System graph network Security conf 1.00 Privileged port 11 in use
Port 11 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
kubernetes/edge/bootstrap/omni/haynes-edge-cluster-template.yaml Ports
medium System graph network Security conf 1.00 Privileged port 13 in use
Port 13 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
kubernetes/edge/bootstrap/omni/haynes-edge-cluster-template.yaml Ports
medium System graph network Security conf 1.00 Privileged port 209 in use
Port 209 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
kubernetes/main/apps/media/plex/app/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 223 in use
Port 223 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
kubernetes/main/apps/home-automation/go2rtc/app/resources/go2rtc.yaml Ports
medium System graph network Security conf 1.00 Privileged port 24 in use
Port 24 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
kubernetes/edge/bootstrap/omni/haynes-edge-cluster-template.yaml Ports
medium System graph network Security conf 1.00 Privileged port 256 in use
Port 256 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
kubernetes/main/apps/home-automation/zwave/app/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 47 in use
Port 47 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
pikvm.yaml Ports
medium System graph network Security conf 1.00 Privileged port 554 in use
Port 554 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
kubernetes/main/apps/home-automation/go2rtc/app/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 58 in use
Port 58 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
pikvm.yaml Ports
medium System graph network Security conf 1.00 Privileged port 675 in use
Port 675 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
kubernetes/main/apps/home-automation/go2rtc/app/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 72 in use
Port 72 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
kubernetes/edge/bootstrap/omni/haynes-edge-cluster-template.yaml Ports
medium System graph network Security conf 1.00 Privileged port 74 in use
Port 74 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
kubernetes/main/bootstrap/omni/cluster-template.yaml Ports
medium System graph network Security conf 1.00 Privileged port 77 in use
Port 77 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
kubernetes/edge/bootstrap/omni/haynes-edge-cluster-template.yaml Ports
medium System graph network Security conf 1.00 Privileged port 83 in use
Port 83 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
kubernetes/edge/bootstrap/omni/haynes-edge-cluster-template.yaml Ports
medium System graph network Security conf 1.00 Privileged port 944 in use
Port 944 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
kubernetes/main/apps/home-automation/zwave/app/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 965 in use
Port 965 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
kubernetes/main/apps/observability/kromgo/app/helmrelease.yaml Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 1 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 10 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `GITHUB_REPO_URL`, `GITHUB_TOKEN`, `MEDIA_DIR`, `PELOTON_ACTIVITY`, `PELOTON_CLASS_LIMIT_PER_ACTIVITY`, `PELOTON_PAGE_SCROLLS`, `PELOTON_PASSWORD`, `PELOTON_USERNAME` + 2 more. Add them (with a placeholder/comment) to .env.example so onboarding doe…
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 56 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 Docker base image is tag-pinned but not digest-pinned: python:3.14-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
scripts/peloton-scrape/Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/peloton-scraper-build.yml:20 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/73d98d8f-8521-459a-b490-8b7741fcbca3/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/73d98d8f-8521-459a-b490-8b7741fcbca3/

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.