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.

T0MYAMMM/distributed-server-monitoring-dashboard

https://github.com/T0MYAMMM/distributed-server-monitoring-dashboard · scanned 2026-06-16 00:28 UTC (2 months, 2 weeks ago)

18 raw signals (0 security + 18 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 18 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 · 18 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

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

Showing 11 of 18 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph security security conf 1.00 Insecure pattern 'exec_used' in frontend/features/integrations/LogSourceGenerator.tsx:38

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

frontend/features/integrations/LogSourceGenerator.tsx:38 Exec used

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — design-system/ui_kits/dashboard/icons.jsx:44

Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html

Fq dangerous html

medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data

A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.

Mock dataCritical flowGenerated repo pattern

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in server-monitor-go/internal/transport/http/middleware/middleware.go:110

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

server-monitor-go/internal/transport/http/middleware/middleware.go:110 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in design-system/ui_kits/dashboard/icons.jsx:44

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

design-system/ui_kits/dashboard/icons.jsx:44 Dangerous innerhtml

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

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 33 placeholder/mock markers across 17 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

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

9 test file(s) for 120 source file(s) (ratio 0.07). 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: ci, 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 quality Integrity conf 1.00 Old/deprecated-named symbol `setOld` in frontend/features/admin/ResetPasswordDialog.tsx:22

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

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/e95078b3-6e79-4dea-9212-5cd1314f2cbb/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e95078b3-6e79-4dea-9212-5cd1314f2cbb/

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.