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

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
Combined
80.6
/100
Security checks
81
0 findings
System graph
81
77.8% cov · 54 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
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
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 80.6/100 with 77.8% coverage. It contains 801 nodes across 20 cross-layer flows, written primarily in mixed languages. Engine surfaced 54 findings — concentrated in quality (41), security (11), api (1). Risk profile is high: 0 critical, 1 high, 12 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 21 of 54 actionable findings. 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 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 security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/detailView.ts:689
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/detailView.ts:689 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/panel.ts:536
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/panel.ts:536 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in src/detailView.ts:1022
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
src/detailView.ts:1022 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/sessionManager.ts:99
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/sessionManager.ts:99 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/usageProvider.ts:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/usageProvider.ts:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/workspaceOpener.ts:20
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/workspaceOpener.ts:20 Node child process
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 16 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 quality Integrity conf 1.00 Old/deprecated-named symbol `cwdOld` in src/foreignWorkspaceManager.test.ts:318
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `knownOld` in src/sessionDiscovery.test.ts:362
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `migrateFromLegacy` in src/sessionDiscovery.ts:164
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `shell_old` in src/sessionManager.test.ts:588
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `wf_old` in src/detailPanel.test.ts:799
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `wf_old` in src/panel.integration.test.ts:930
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `wf_old` in src/workflowDiscovery.test.ts:110
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
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/detailView.ts (1072 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/panel.integration.test.ts (1161 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/sessionDiscovery.ts (1251 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/sessionManager.ts (1774 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/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.