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.

s0len/solen-ops

https://github.com/s0len/solen-ops · scanned 2026-06-15 23:59 UTC (2 months, 3 weeks ago)

30 raw signals (0 security + 30 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 30 actionable findings from 1 signal source. 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: 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 84.1/100 with 100.0% coverage. It contains 1692 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 30 findings — concentrated in network (18), quality (8), api (1). Risk profile is low: 0 critical, 0 high, 23 medium. Recommended next step: open the network layer findings first — that's where the highest-impact wins live.

Showing 26 of 30 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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
CLAUDE.md VerificationClaude instruction
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 security security conf 1.00 Insecure pattern 'cors_wildcard' in kubernetes/apps/default/go2rtc/app/helmrelease.yaml:96
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
kubernetes/apps/default/go2rtc/app/helmrelease.yaml:96 Cors wildcard
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/apps/media/dispatcharr/app/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 124 in use
Port 124 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/apps/default/home-assistant/app/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 139 in use
Port 139 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/apps/media/flaresolverr/app/helmrelease.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/apps/security/kanidm/app/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 28 in use
Port 28 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/apps/media/plex/kometa/configs/config.yaml Ports
medium System graph network Security conf 1.00 Privileged port 389 in use
Port 389 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/apps/default/glauth/app/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 391 in use
Port 391 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/apps/observability/gatus/app/helmrelease.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/apps/default/go2rtc/app/helmrelease.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/apps/default/go2rtc/app/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 774 in use
Port 774 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/apps/default/tvsportsdb/app/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 79 in use
Port 79 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/apps/media/bazarr/app/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 89 in use
Port 89 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/apps/media/unpackerr/app/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 896 in use
Port 896 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/apps/network/unifi-controller/app/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 943 in use
Port 943 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/apps/default/searxng/app/helmrelease.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/apps/media/autobrr/app/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 96 in use
Port 96 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/apps/media/prowlarr/app/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 969 in use
Port 969 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/apps/default/tandoor/app/helmrelease.yaml Ports
medium System graph network Security conf 1.00 Privileged port 976 in use
Port 976 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/apps/media/plex/plex-auto-languages/helmrelease.yaml Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 2 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 9 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 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/9b48de6c-b28a-4cc6-b645-f45612307470/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9b48de6c-b28a-4cc6-b645-f45612307470/

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.