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.

cloudy064/sb-easy

https://github.com/cloudy064/sb-easy · scanned 2026-06-17 01:49 UTC (1 month, 1 week ago)

13 raw signals (0 security + 13 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -9.4 (diff) · 13 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 13 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

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

Showing 13 of 13 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 backend/src/services/subscription.rs

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

backend/src/services/subscription.rs:255

critical System graph security Secrets conf 1.00 Possible secret in README.md

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

README.md:31

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: 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 GitHub Action is tag-pinned rather than SHA-pinned

docker/build-push-action@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

.github/workflows/ci.yml:48 CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/stores/auth.ts:19

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

frontend/src/stores/auth.ts:19 Local storage auth token

medium System graph network Security conf 1.00 Privileged port 3 in use

Port 3 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

scripts/backup.sh Ports

medium System graph network Security conf 1.00 Privileged port 30 in use

Port 30 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

scripts/backup.sh Ports

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

0 test file(s) for 51 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

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

Multiple low-cost hardening controls are missing together: license, tests. 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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/views/MonitorView.vue:70

A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label

Fq button no label

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/views/ProfilesView.vue:59

Fq button no label

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/fde35041-f34a-4916-85d3-b2c766a5489d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/fde35041-f34a-4916-85d3-b2c766a5489d/

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.