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.

toouur/foursquare-dashboard

https://github.com/toouur/foursquare-dashboard · scanned 2026-06-16 00:40 UTC (2 months, 1 week ago)

53 raw signals (0 security + 53 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
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 66.5/100 with 88.9% coverage. It contains 497 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 53 findings — concentrated in security (21), quality (18), cicd (10). Risk profile is high: 0 critical, 1 high, 33 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 37 of 44 actionable findings. 53 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 Agent instructions conf 1.00 Agent instruction/config may expose a secret: CLAUDE.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
CLAUDE.md:67 SecretsClaude instruction
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — functions/api/search-venues.js:50
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 — functions/api/venue-tips.js:27
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 8 occurrences 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.
8 files, 8 locations
.github/workflows/add-checkin-photos.yml
.github/workflows/add-venue-rating.yml
.github/workflows/delete-checkin.yml
.github/workflows/fetch-lists.yml
.github/workflows/fetch-venue-rating.yml
.github/workflows/fix-overlaps.yml
.github/workflows/release.yml
.github/workflows/update-dashboard.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in feed.html:654
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
feed.html:654 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in flights.html:323
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
flights.html:323 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in guide.html:349
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
guide.html:349 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in search.html:123
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
search.html:123 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in world_cities.html:198
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
world_cities.html:198 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in year-2012.html:287
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
year-2012.html:287 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in year-2013.html:287
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
year-2013.html:287 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in year-2014.html:287
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
year-2014.html:287 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in year-2015.html:287
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
year-2015.html:287 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in year-2016.html:287
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
year-2016.html:287 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in year-2017.html:287
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
year-2017.html:287 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in year-2018.html:289
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
year-2018.html:289 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in year-2019.html:289
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
year-2019.html:289 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in year-2020.html:303
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
year-2020.html:303 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in year-2021.html:293
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
year-2021.html:293 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in year-2022.html:293
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
year-2022.html:293 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in year-2023.html:287
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
year-2023.html:287 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in year-2024.html:287
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
year-2024.html:287 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in year-2025.html:290
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
year-2025.html:290 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in year-2026.html:287
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
year-2026.html:287 Direct innerhtml assignment
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/fetch_categories.py:35
`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 Tests conf 1.00 Very low test-to-source ratio
1 test file(s) for 51 source file(s) (ratio 0.02). 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 190 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 cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/upload-artifact@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 2 locations
.github/workflows/backup-d1.yml:50
.github/workflows/resync-all.yml:65
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/gen_guide.py:build_page, scripts/gen_year_pages.py:build_page This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 7 places
Functions with the same first-5-line body hash: scripts/rate_venue.py:resolve_token, scripts/refresh_venue.py:resolve_token, scripts/fetch_venue_rating.py:resolve_token, scripts/fetch_tips.py:resolve_token This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://j…
duplicatesduplication
low System graph software Dead code conf 1.00 Possibly dead Python function: summarise
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/flights.py:301
low System graph software Dead code conf 1.00 Possibly dead Python function: task
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/find_closed_venue_tips.py:247
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 — workers/checkin-poller/worker.js:27
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: scripts/gen_year_pages.py (1551 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/metrics.py (2393 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/a98b7e39-d1ff-4816-9f87-fed21ca66af8/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a98b7e39-d1ff-4816-9f87-fed21ca66af8/

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.