streamplace/streamplace

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.

80 of your 559 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 13.82s · analysis 89.33s · 18.5 MB · GitHub API rate-limit (preflight)

https://github.com/streamplace/streamplace · scanned 2026-06-05 17:38 UTC (4 days, 22 hours ago) · 10 languages

853 raw signals (485 security + 368 graph) 3rd percentile · Go · large (100-500K LoC) System graph score 67 (lower by 14)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 22 hours ago · v2 · 563 actionable findings from 2 signal sources. 105 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 159 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	20.1	0.25	5.03
`testing_score`	40.0	0.20	8.00
`documentation_score`	60.0	0.15	9.00
`practices_score`	80.0	0.15	12.00
`code_quality`	65.1	0.10	6.51
Overall		1.00	53.3

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 14 High 235 Medium 97 Low 168 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 404 System graph 159 Crowd 0 Layer: Quality 60 Security 36 Software 387 Cicd 4 Api 1 Frontend 75

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Commented-out code 11 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

11 matching findings on this repo

info Commented-code block (6 lines) in js/components/src/components/ui/menu.tsx:282
info Commented-code block (6 lines) in js/components/src/components/mobile-player/ui…
info Commented-code block (5 lines) in js/components/src/hooks/useAvatar.ts:5
info Commented-code block (11 lines) in js/components/src/streamplace-store/streampl…
info Commented-code block (5 lines) in js/app/metro.config.js:21
info Commented-code block (7 lines) in js/app/scripts/gen-emoji-data.js:7
info Commented-code block (5 lines) in js/app/components/mobile/player.tsx:509
info Commented-code block (5 lines) in js/app/hooks/useVideoList.ts:9
info Commented-code block (13 lines) in js/app/src/shell.tsx:277
info Commented-code block (5 lines) in js/app/src/screens/upload.tsx:647
info Commented-code block (7 lines) in js/app/src/screens/app-return.tsx:7

View all commented-out code findings →

Config drift 13 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

12 matching findings on this repo

medium [AUC009] Sensitive function route lacks elevated authorization evidence: A rout… pkg/spxrpc/stubs.go:293
medium npm package `@config-plugins/react-native-webrtc` is 5 major version(s) behind … js/config-react-native-webrtc/package.json
low @smithy/config-resolver: GHSA-6475-r3vj-m8vf pnpm-lock.yaml
low File has no detected symbols: js/docs/src/content.config.ts
low File has no detected symbols: js/desktop/webpack.main.config.ts
low File has no detected symbols: js/desktop/forge.config.ts
low File has no detected symbols: js/desktop/webpack.renderer.config.ts
low File has no detected symbols: js/components/i18next.config.js
low File has no detected symbols: js/app/exportClientExpoConfig.js
low File has no detected symbols: js/app/metro.config.js
low File has no detected symbols: js/app/babel.config.js
low Stray `console.log` in TS/JS — js/app/exportClientExpoConfig.js:11

View all config drift findings →

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/f11a2d98-be47-4315-afef-70785f2a4ae6/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f11a2d98-be47-4315-afef-70785f2a4ae6/

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.