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.

stagewise-io/stagewise

https://github.com/stagewise-io/stagewise · scanned 2026-06-16 00:21 UTC (2 months, 2 weeks ago)

365 raw signals (0 security + 365 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 337 actionable findings from 1 signal source. 28 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 · 337 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 5 Medium 77 Low 77 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 337 Crowd 0 Layer: Frontend 123 Hardware 3 Security 47 Cicd 4 Quality 151 Api 9

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.

Legacy markers 1 finding

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

1 matching finding on this repo

low Old/deprecated-named symbol `canReplayLegacy` in packages/agent-core/src/agents…

View all legacy markers findings →

Commented-out code 94 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/`.

12 matching findings on this repo

info Commented-code block (5 lines) in apps/update-server/src/releases.ts:266
info Commented-code block (8 lines) in apps/update-server/src/routes.ts:153
info Commented-code block (7 lines) in apps/website/src/components/posthog-provider.…
info Commented-code block (5 lines) in apps/website/src/lib/auth-client.ts:3
info Commented-code block (6 lines) in apps/stagewise-cli/src/cli-chat-agent.ts:11
info Commented-code block (6 lines) in apps/browser/vite.backend.config.ts:26
info Commented-code block (6 lines) in apps/browser/vite.ui.config.ts:46
info Commented-code block (8 lines) in apps/browser/src/web-content-preload/stealth.…
info Commented-code block (5 lines) in apps/browser/src/shared/available-models.ts:1…
info Commented-code block (5 lines) in apps/browser/src/shared/chromium-errors/codes…
info Commented-code block (5 lines) in apps/browser/src/shared/utils/attachment-file…
info Commented-code block (9 lines) in apps/browser/src/ui/screens/index.tsx:11

View all commented-out code findings →

Config drift 3 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.

3 matching findings on this repo

high Agent instruction/config may expose a secret: apps/browser/bundled/plugins/post… apps/browser/bundled/plugins/posthog/SKILL.md:411
info Commented-code block (6 lines) in apps/browser/vite.backend.config.ts:26
info Commented-code block (6 lines) in apps/browser/vite.ui.config.ts:46

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/5ff5cc89-51fa-498b-b564-be2442192682/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5ff5cc89-51fa-498b-b564-be2442192682/

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.