shuuuvuuu/boundary-lab-portal — Repobility public scan

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

shuuuvuuu/boundary-lab-portal

https://github.com/shuuuvuuu/boundary-lab-portal · scanned 2026-06-16 00:12 UTC (2 months, 2 weeks ago)

78 raw signals (0 security + 78 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 67 actionable findings from 1 signal source. 11 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

Security checks

100.0% cov · 67 findings

click to filter

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

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 60.7/100 with 100.0% coverage. It contains 2919 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 78 findings — concentrated in quality (42), frontend (14), cicd (10). Risk profile is high: 0 critical, 2 high, 31 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 32 of 67 actionable findings. 78 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.

high System graph security security conf 1.00 Insecure pattern 'new_function_used' in src/instrumentation.ts:26

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

src/instrumentation.ts:26 New function used

high System graph security security conf 1.00 Insecure pattern 'new_function_used' in src/lib/otel/active-span.ts:16

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

src/lib/otel/active-span.ts:16 New function used

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/app/blog/[slug]/page.tsx:60

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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/app/admin/ops/inv/graph/auditLog.ts:54

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/app/api/admin/ops/slo/route.ts:43

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/components/DiscoverTab.tsx:33

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/components/EventsTab.tsx:26

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/components/MetaNetworkExplorer.tsx:93

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/components/PersonalTab.tsx:25

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/components/world/CollectionAddControl.tsx:76

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/components/world/FavoriteWorldsPanel.tsx:41

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/components/world/ReviewsModal.tsx:45

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/components/world/WorldEditModal.tsx:96

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/lib/backup/r2.ts:157

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/lib/replays/r2-storage.ts:184

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: docs/architecture/SKILL.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.

docs/architecture/SKILL.md VerificationSkill file

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 cicd CI/CD security conf 1.00 9 occurrences GitHub Action is tag-pinned rather than SHA-pinned

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

lines 24, 27, 35, 43, 65, 68, 76, 84, +1 more

.github/workflows/docker.yml:24, 27, 35, 43, 65, 68, 76, 84, +1 more (9 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/docker.yml CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in src/app/api/public/status/route.ts:41

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

src/app/api/public/status/route.ts:41 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/app/blog/[slug]/page.tsx:60

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

src/app/blog/[slug]/page.tsx:60 Dangerous innerhtml

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/app/admin/replays/[sessionId]/ReplayClient.tsx:121

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

src/app/admin/replays/[sessionId]/ReplayClient.tsx:121 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/lib/jobs/synthetic-login.ts:1

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

src/lib/jobs/synthetic-login.ts:1 Node child process

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

Found 133 placeholder/mock markers across 42 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

17 test file(s) for 360 source file(s) (ratio 0.05). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Integrity conf 1.00 63 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `API_STORM_RPM_THRESHOLD`, `APP_VERSION`, `BOUNDARY_INTERNAL_SECRET`, `BOUNDARY_INTERNAL_URL`, `BURN_RATE_DISABLED`, `DO_NODE_EXPORTER_URL`, `EXTERNAL_STATUS_RETENTION_DAYS`, `FRONTEND_INGEST_ALLOWED_ORIGINS` + 55 more. Add them (with a placeholder…

config drift

low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-bookworm-slim

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

lines 1, 11

services/hubs-entry-sidecar/Dockerfile:1, 11 (2 hits)

containersPinned dependencies

low System graph hardware Supply chain conf 1.00 3 occurrences Docker base image is tag-pinned but not digest-pinned: node:22-alpine

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

lines 2, 9, 25

Dockerfile:2, 9, 25 (3 hits)

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

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

low System graph quality Complexity conf 1.00 Very large file: src/app/admin/ops/cost/CostClient.tsx (1385 lines)

Files with >800 lines often hide complexity hotspots and discourage tests.

low System graph quality Complexity conf 1.00 Very large file: src/lib/jobs/weekly-report.ts (1766 lines)

Files with >800 lines often hide complexity hotspots and discourage tests.

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/594a6d7f-6ef0-4d3e-a226-8454feec7464/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/594a6d7f-6ef0-4d3e-a226-8454feec7464/

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.