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

ursm/capybara-simulated

https://github.com/ursm/capybara-simulated · scanned 2026-06-16 00:46 UTC (2 months, 1 week ago)

242 raw signals (0 security + 242 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
59.4
/100
Security checks
59
0 findings
System graph
59
88.9% cov · 237 findings
Critical
1
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 1 High 25 Medium 98 Low 13 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 237 Crowd 0 Layer: Software 1 Frontend 13 Network 1 Security 102 Cicd 1 Quality 119
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 59.4/100 with 88.9% coverage. It contains 3353 nodes across 10 cross-layer flows, written primarily in mixed languages. Engine surfaced 242 findings — concentrated in quality (124), security (102), frontend (13). Risk profile is high: 1 critical, 25 high, 98 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 42 of 237 actionable findings. 242 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.

high System graph security security conf 1.00 Insecure pattern 'eval_used' in lib/capybara/simulated/js/bridge.bundle.js:20086
Found a known-risky pattern (eval_used). Review and replace if possible.
lib/capybara/simulated/js/bridge.bundle.js:20086 Eval used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in lib/capybara/simulated/js/bridge.bundle.js:1069
Found a known-risky pattern (new_function_used). Review and replace if possible.
lib/capybara/simulated/js/bridge.bundle.js:1069 New function used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in lib/capybara/simulated/js/src/bridge.entry.js:1056
Found a known-risky pattern (new_function_used). Review and replace if possible.
lib/capybara/simulated/js/src/bridge.entry.js:1056 New function used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in lib/capybara/simulated/js/src/dispatch.js:232
Found a known-risky pattern (new_function_used). Review and replace if possible.
lib/capybara/simulated/js/src/dispatch.js:232 New function used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in lib/capybara/simulated/js/src/events.js:831
Found a known-risky pattern (new_function_used). Review and replace if possible.
lib/capybara/simulated/js/src/events.js:831 New function used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — lib/capybara/simulated/js/bridge.bundle.js:14700
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 — lib/capybara/simulated/js/src/fetch.js:1
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 — script/vendor_wpt.mjs:62
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 — spec/wpt/common/security-features/resources/common.sub.js:1274
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 — spec/wpt/encoding/textdecoder-mistakes.any.js:551
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 — spec/wpt/resources/testharness.js:5034
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 — spec/wpt/url/IdnaTestV2-removed.any.js:3
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 — spec/wpt/url/IdnaTestV2.any.js:3
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 — spec/wpt/url/percent-encoding.window.js:1
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 — spec/wpt/url/resources/a-element-origin.js:2
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 — spec/wpt/url/resources/a-element.js:2
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 — spec/wpt/url/toascii.window.js:1
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 — spec/wpt/url/url-constructor.any.js:54
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 — spec/wpt/url/url-origin.any.js:2
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 — spec/wpt/url/url-setters-a-area.window.js:9
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 — spec/wpt/url/url-setters.any.js:9
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 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 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/release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in lib/capybara/simulated/js/src/host-queries.js:157
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
lib/capybara/simulated/js/src/host-queries.js:157 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in lib/capybara/simulated/trace_viewer.html:175
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
lib/capybara/simulated/trace_viewer.html:175 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in lib/capybara/simulated/js/src/host-queries.js:158
Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.
lib/capybara/simulated/js/src/host-queries.js:158 Direct outerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in lib/capybara/simulated/trace_viewer.html:312
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
lib/capybara/simulated/trace_viewer.html:312 Domparser html parse
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — spec/wpt/url/tools/IdnaTestV2-parser.py:25
`urllib.request.urlopen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 29 placeholder/mock markers across 9 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
20 test file(s) for 321 source file(s) (ratio 0.06). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: spec/wpt/common/security-features/subresource/static-import.py:get_csp_value, spec/wpt/common/security-features/tools/generate.py:get_csp_value This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-h…
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: spec/wpt/common/redirect.py:main, spec/wpt/common/redirect-opt-in.py:main, spec/wpt/common/slow-redirect.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or documen…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `data_old` in spec/wpt/url/tools/IdnaTestV2-compare.py:9
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — spec/wpt/resources/testharness.js:2844
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: lib/capybara/simulated/js/bridge.bundle.js (20581 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: lib/capybara/simulated/js/src/bridge.entry.js (1881 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: lib/capybara/simulated/js/src/cascade.js (1291 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: lib/capybara/simulated/js/src/dom-nodes.js (6685 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: lib/capybara/simulated/js/src/form-fields.js (1398 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: spec/wpt/dom/observable/tentative/observable-from.any.js (1741 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: spec/wpt/resources/testharness.js (5207 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/1ecd361c-8596-4e13-9627-2e2274fb9f2c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/1ecd361c-8596-4e13-9627-2e2274fb9f2c/

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.