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.

snowmeltio/serac

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

54 raw signals (0 security + 54 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 54 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 12 Low 13 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 54 Crowd 0 Layer: Api 1 Security 11 Cicd 1 Quality 41

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 `migrateFromLegacy` in src/sessionDiscovery.ts:164

View all legacy markers findings →

Commented-out code 26 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 (6 lines) in confirm-publish.mjs:2
info Commented-code block (5 lines) in src/sessionManager.ts:313
info Commented-code block (5 lines) in src/panel.ts:251
info Commented-code block (6 lines) in src/sessionManager.hookEnrichment.test.ts:195
info Commented-code block (5 lines) in src/workflowDiscovery.ts:345
info Commented-code block (13 lines) in src/teammateInbox.ts:5
info Commented-code block (12 lines) in src/panelRender.ts:424
info Commented-code block (5 lines) in src/subagentTailerManager.ts:180
info Commented-code block (5 lines) in src/sessionManager.bubble.test.ts:168
info Commented-code block (6 lines) in src/teamDiscovery.ts:167
info Commented-code block (6 lines) in src/foreignWorkspaceManager.ts:136
info Commented-code block (7 lines) in src/teamManifest.ts:113

View all commented-out code 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/607e7906-f74d-4f37-b7bd-91f91d97a13f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/607e7906-f74d-4f37-b7bd-91f91d97a13f/

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.