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.

shade-tree-software/campgrounds

https://github.com/shade-tree-software/campgrounds · scanned 2026-06-16 00:08 UTC (2 months, 2 weeks ago)

155 raw signals (0 security + 155 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 152 findings

Severity distribution — click a segment to filter

Active filters: severity: low × excluding tests × Reset all

Severity: Critical 0 High 58 Medium 17 Low 65 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 152 Crowd 0 Layer: Software 1 Frontend 3 Security 45 Cicd 1 Quality 31 Api 71

Exclude dismissed / FP Exclude test files

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.9/100 with 88.9% coverage. It contains 544 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 155 findings — concentrated in api (71), security (45), quality (34). Risk profile is high: 0 critical, 58 high, 17 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 65 of 152 actionable findings. 155 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.

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 18 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 'debug_true' in ekko_trips_app.py:4186

Found a known-risky pattern (debug_true). Review and replace if possible.

ekko_trips_app.py:4186 Debug true

low System graph security security conf 1.00 Insecure pattern 'debug_true' in summer_seeker_app.py:133

Found a known-risky pattern (debug_true). Review and replace if possible.

summer_seeker_app.py:133 Debug true

low System graph quality Tests conf 1.00 Low test-to-source ratio

4 tests / 17 src (ratio 0.24).

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: ekko_trips_app.py:trips_map, ekko_trips_app.py:trips_calendar 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.

4 occurrences

repo-level (4 hits)

duplicatesduplication

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 Integrity conf 1.00 Old/deprecated-named symbol `is_old` in ekko_trips_app.py:2417

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 software Dead code conf 1.00 Possibly dead Python function: lookup

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

ekko_trips_app.py:2362

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 — static/trip-detail/map.js:201

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 — static/trip-detail/timeline.js:906

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 `progress_callback` (body is just `pass`/`return`) — summer_seeker_app.py:88

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph api Wiring conf 1.00 Unused endpoint: ANY /

`summer_seeker_app.py` declares `ANY /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin/users

`ekko_trips_app.py` declares `ANY /admin/users` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/campgrounds/<int:cg_id>

`ekko_trips_app.py` declares `ANY /api/campgrounds/<int:cg_id>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/campgrounds/all

`ekko_trips_app.py` declares `ANY /api/campgrounds/all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/geocode

`ekko_trips_app.py` declares `ANY /api/geocode` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/reverse-geocode

`ekko_trips_app.py` declares `ANY /api/reverse-geocode` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/trips

`ekko_trips_app.py` declares `ANY /api/trips` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/trips/<int:trip_id>

`ekko_trips_app.py` declares `ANY /api/trips/<int:trip_id>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/trips/<int:trip_id>/events

`ekko_trips_app.py` declares `ANY /api/trips/<int:trip_id>/events` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/trips/<int:trip_id>/events/<int:event_idx>

`ekko_trips_app.py` declares `ANY /api/trips/<int:trip_id>/events/<int:event_idx>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/trips/<int:trip_id>/relocate-pings

`ekko_trips_app.py` declares `ANY /api/trips/<int:trip_id>/relocate-pings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/trips/<int:trip_id>/stays

`ekko_trips_app.py` declares `ANY /api/trips/<int:trip_id>/stays` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/trips/<int:trip_id>/stays/<int:stay_idx>

`ekko_trips_app.py` declares `ANY /api/trips/<int:trip_id>/stays/<int:stay_idx>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/trips/<int:trip_id>/suppress-pings

`ekko_trips_app.py` declares `ANY /api/trips/<int:trip_id>/suppress-pings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/trips/<int:trip_id>/tid-overrides

`ekko_trips_app.py` declares `ANY /api/trips/<int:trip_id>/tid-overrides` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/trips/<int:trip_id>/track

`ekko_trips_app.py` declares `ANY /api/trips/<int:trip_id>/track` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/users

`ekko_trips_app.py` declares `ANY /api/users` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/users/<username>

`ekko_trips_app.py` declares `ANY /api/users/<username>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /campgrounds/climate

`ekko_trips_app.py` declares `ANY /campgrounds/climate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /campgrounds/manage

`ekko_trips_app.py` declares `ANY /campgrounds/manage` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /campgrounds/map

`ekko_trips_app.py` declares `ANY /campgrounds/map` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /campgrounds/waterfront

`ekko_trips_app.py` declares `ANY /campgrounds/waterfront` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /geocode

`summer_seeker_app.py` declares `ANY /geocode` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /login

`ekko_trips_app.py` declares `ANY /login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /logout

`ekko_trips_app.py` declares `ANY /logout` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /offline

`ekko_trips_app.py` declares `ANY /offline` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /search

`summer_seeker_app.py` declares `ANY /search` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /sw-reset

`ekko_trips_app.py` declares `ANY /sw-reset` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /sw.js

`ekko_trips_app.py` declares `ANY /sw.js` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /thumb/<path:subpath>

`ekko_trips_app.py` declares `ANY /thumb/<path:subpath>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips

`ekko_trips_app.py` declares `ANY /trips` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/<int:trip_id>

`ekko_trips_app.py` declares `ANY /trips/<int:trip_id>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/<int:trip_id>/events/<int:event_idx>/caption

`ekko_trips_app.py` declares `ANY /trips/<int:trip_id>/events/<int:event_idx>/caption` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/<int:trip_id>/events/<int:event_idx>/photos

`ekko_trips_app.py` declares `ANY /trips/<int:trip_id>/events/<int:event_idx>/photos` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/<int:trip_id>/events/<int:event_idx>/photos/<filename>

`ekko_trips_app.py` declares `ANY /trips/<int:trip_id>/events/<int:event_idx>/photos/<filename>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documentin…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/<int:trip_id>/events/<int:event_idx>/photos/<filename>/restore

`ekko_trips_app.py` declares `ANY /trips/<int:trip_id>/events/<int:event_idx>/photos/<filename>/restore` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or do…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/<int:trip_id>/events/<int:event_idx>/reorder

`ekko_trips_app.py` declares `ANY /trips/<int:trip_id>/events/<int:event_idx>/reorder` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/<int:trip_id>/events/<int:event_idx>/upload

`ekko_trips_app.py` declares `ANY /trips/<int:trip_id>/events/<int:event_idx>/upload` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/<int:trip_id>/move-photo

`ekko_trips_app.py` declares `ANY /trips/<int:trip_id>/move-photo` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/<int:trip_id>/stays/<int:stay_idx>/caption

`ekko_trips_app.py` declares `ANY /trips/<int:trip_id>/stays/<int:stay_idx>/caption` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/<int:trip_id>/stays/<int:stay_idx>/photos

`ekko_trips_app.py` declares `ANY /trips/<int:trip_id>/stays/<int:stay_idx>/photos` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/<int:trip_id>/stays/<int:stay_idx>/photos/<filename>

`ekko_trips_app.py` declares `ANY /trips/<int:trip_id>/stays/<int:stay_idx>/photos/<filename>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/<int:trip_id>/stays/<int:stay_idx>/photos/<filename>/restore

`ekko_trips_app.py` declares `ANY /trips/<int:trip_id>/stays/<int:stay_idx>/photos/<filename>/restore` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docu…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/<int:trip_id>/stays/<int:stay_idx>/reorder

`ekko_trips_app.py` declares `ANY /trips/<int:trip_id>/stays/<int:stay_idx>/reorder` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/<int:trip_id>/stays/<int:stay_idx>/upload

`ekko_trips_app.py` declares `ANY /trips/<int:trip_id>/stays/<int:stay_idx>/upload` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/calendar

`ekko_trips_app.py` declares `ANY /trips/calendar` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/list

`ekko_trips_app.py` declares `ANY /trips/list` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/map

`ekko_trips_app.py` declares `ANY /trips/map` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/poster

`ekko_trips_app.py` declares `ANY /trips/poster` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /trips/stats

`ekko_trips_app.py` declares `ANY /trips/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph quality Complexity conf 1.00 Very large file: ekko_trips_app.py (4186 lines)

Files with >800 lines often hide complexity hotspots and discourage tests.

low System graph quality Complexity conf 1.00 Very large file: static/trip-detail/map.js (1072 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/01090711-7cab-4c10-9f8f-aaf2467d8619/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/01090711-7cab-4c10-9f8f-aaf2467d8619/

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.