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

susansimongoh/dopey

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

37 raw signals (0 security + 37 graph)

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

Complete repo analysis

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

JSON
Combined
95.2
/100
Security checks
95
0 findings
System graph
95
88.9% cov · 37 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 0 Medium 12 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 37 Crowd 0 Layer: Software 10 Frontend 5 Security 8 Cicd 1 Quality 13
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 95.2/100 with 88.9% coverage. It contains 217 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 37 findings — concentrated in quality (13), software (10), security (8). Risk profile is low: 0 critical, 0 high, 12 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 32 of 37 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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apify-tier3-keyword-search.js:151
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 — netlify/lib/sps.mjs:26
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 — supabase/functions/daily-scrape/index.ts:21
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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in launch_server.py:711
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
launch_server.py:711 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in sps-media-monitor-redesigned.html:1112
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
sps-media-monitor-redesigned.html:1112 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in sps-media-monitor.html:435
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
sps-media-monitor.html:435 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in sps-monitor.html:874
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
sps-monitor.html:874 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in sps-monitor.html:888
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
sps-monitor.html:888 Local storage auth token
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
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
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 12 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 33 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 security security conf 1.00 Insecure pattern 'document_write' in sps-media-monitor-redesigned.html:1352
Found a known-risky pattern (document_write). Review and replace if possible.
sps-media-monitor-redesigned.html:1352 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in sps-monitor.html:1704
Found a known-risky pattern (document_write). Review and replace if possible.
sps-monitor.html:1704 Document write
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Docs conf 1.00 No README detected
No README file was found. Generated repos without README context are hard to operate, validate, or safely hand off.
ReadmeRepo hardeningGenerated repo pattern
low System graph software Dead code conf 1.00 Possibly dead Python function: do_OPTIONS
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
launch_server.py:605
low System graph software Dead code conf 1.00 Possibly dead Python function: do_POST
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
launch_server.py:653
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_bing_news
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
launch_server.py:149
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_facebook
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
launch_server.py:319
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_google_news
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
launch_server.py:121
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_instagram
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
launch_server.py:302
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_reddit_combined
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
launch_server.py:176
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_tiktok
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
launch_server.py:282
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_youtube
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
launch_server.py:358
low System graph software Dead code conf 1.00 Possibly dead Python function: log_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
launch_server.py:724
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 — apify-tier3-keyword-search.js:181
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — sps-media-monitor-apify-integration.js:83
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — sps-media-monitor-supabase-integration.js:60
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 Integrity conf 1.00 Stub function `log_message` (body is just `pass`/`return`) — launch_server.py:724
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
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/5b52dcc2-fe1b-4b07-af14-5cc69a8903d2/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/5b52dcc2-fe1b-4b07-af14-5cc69a8903d2/

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.