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.

withremyinc/stream

https://github.com/withremyinc/stream · scanned 2026-06-16 00:58 UTC (2 months, 1 week ago)

28 raw signals (0 security + 28 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 19 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

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

Showing 14 of 19 actionable findings. 28 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.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/bench-geojson.mjs:104

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 — scripts/bench-xml.mjs:35

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

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

3 files, 3 locations

.github/workflows/ci.yml:27

.github/workflows/docs.yml:25

.github/workflows/publish.yml:28

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/docs.yml 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/publish.yml CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/index.html:1434

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

docs/index.html:1434 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in scripts/build-docs.mjs:1570

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

scripts/build-docs.mjs:1570 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/bench-xml.mjs:16

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

scripts/bench-xml.mjs:16 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/serve-docs.mjs:12

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

scripts/serve-docs.mjs:12 Node child process

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

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

actions/checkout@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

3 files, 8 locations

.github/workflows/docs.yml:22, 31, 44, 57 (4 hits)

.github/workflows/ci.yml:24, 33 (2 hits)

.github/workflows/publish.yml:25, 34 (2 hits)

CI/CD securitySupply chainGithub actions

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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/index.ts:196

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

low System graph quality Complexity conf 1.00 Very large file: scripts/build-docs.mjs (1653 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/ab189648-5419-4115-9d90-8110707189a9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ab189648-5419-4115-9d90-8110707189a9/

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.