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

SimpleTrailer/simpletrailer

https://github.com/SimpleTrailer/simpletrailer · scanned 2026-06-16 00:13 UTC (2 months, 2 weeks ago)

84 raw signals (0 security + 84 graph)

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

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 79 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
55.4
/100
Security checks
55
0 findings
System graph
55
88.9% cov · 79 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 1 Medium 57 Low 11 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 79 Crowd 0 Layer: Frontend 5 Network 2 Security 36 Cicd 2 Quality 34
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 55.4/100 with 88.9% coverage. It contains 436 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 84 findings — concentrated in security (37), quality (34), cicd (6). Risk profile is high: 2 critical, 1 high, 57 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 70 of 79 actionable findings. 84 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.

critical System graph security Secrets conf 1.00 2 occurrences Possible secret in setup-traccar-server.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 74, 75
setup-traccar-server.sh:74, 75 (2 hits)
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:34 SecretsClaude instruction
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — api/_push-sender.js:77
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 — api/cron/budget-optimizer.js: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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — api/cron/bug-triager.js:41
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 — api/cron/competitor-watcher.js:69
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 — api/cron/legal-quarterly-audit.js:91
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 — api/cron/midweek-check.js:59
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 — api/cron/social-media-generator.js:108
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 — api/cron/sync-tracker-positions.js:41
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 — api/cron/tracker-watchdog.js:52
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 — api/cron/weekly-advisor.js:87
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 — api/cron/weekly-ratgeber-generator.js:102
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 — api/process-return.js:83
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 — api/trailer-position.js:48
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 — mobile-app/server-stub/delete-account.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 — mobile-app/server-stub/save-push-token.js:10
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 — sw.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 Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci, lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, lockfile. 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 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 Action is tag-pinned rather than SHA-pinned
android-actions/setup-android@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
mobile-app/.github/workflows/android-build.yml:49 CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in api/booking.js:16
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api/booking.js:16 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in api/chat.js:171
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api/chat.js:171 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in api/contact.js:23
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api/contact.js:23 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in api/create-payment-intent.js:18
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api/create-payment-intent.js:18 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in api/get-availability.js:6
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api/get-availability.js:6 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in api/get-trailers.js:5
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api/get-trailers.js:5 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in api/health.js:9
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api/health.js:9 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in api/heartbeat.js:14
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api/heartbeat.js:14 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in api/identity.js:23
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api/identity.js:23 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in api/live-visitors.js:15
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api/live-visitors.js:15 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in api/newsletter-subscribe.js:19
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api/newsletter-subscribe.js:19 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in api/notify-when-available.js:16
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api/notify-when-available.js:16 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in api/process-return.js:9
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api/process-return.js:9 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in api/send-reminders.js:14
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api/send-reminders.js:14 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in mobile-app/server-stub/delete-account.js:22
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
mobile-app/server-stub/delete-account.js:22 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in mobile-app/server-stub/save-push-token.js:24
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
mobile-app/server-stub/save-push-token.js:24 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in account.html:548
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
account.html:548 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin.html:1291
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin.html:1291 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in anleitung.html:563
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
anleitung.html:563 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in booking.html:1214
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
booking.html:1214 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in chat-widget.js:461
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
chat-widget.js:461 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in hero-light.html:4111
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
hero-light.html:4111 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in i18n.js:995
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
i18n.js:995 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in index.html:4294
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
index.html:4294 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in precheck.html:369
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
precheck.html:369 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in return.html:391
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
return.html:391 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in hero-light.html:3990
Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.
hero-light.html:3990 Direct outerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in index.html:4173
Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.
index.html:4173 Direct outerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in account.html:364
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
account.html:364 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in booking.html:1832
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
booking.html:1832 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in mobile-app/www/api-client.js:100
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
mobile-app/www/api-client.js:100 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in mobile-app/www/native-bridge.js:74
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
mobile-app/www/native-bridge.js:74 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in native-bridge.js:77
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
native-bridge.js:77 Local storage auth token
medium System graph network Security conf 1.00 Privileged port 3 in use
Port 3 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
setup-traccar-server.sh Ports
medium System graph network Security conf 1.00 Privileged port 4 in use
Port 4 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
setup-traccar-server.sh Ports
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 65 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 8 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 5 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 33, 36, 43, 69, 104
mobile-app/.github/workflows/android-build.yml:33, 36, 43, 69, 104 (5 hits)
CI/CD securitySupply chainGithub actions
low System graph security security conf 1.00 Insecure pattern 'document_write' in admin.html:1742
Found a known-risky pattern (document_write). Review and replace if possible.
admin.html:1742 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 dependencies conf 1.00 Node manifest has dependencies but no lockfile: package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `st_chat_history_v2` in chat-widget.js:13
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 — api/cron/sync-tracker-positions.js:137
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 — api/stripe-webhook.js:53
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 — mobile-app/www/native-bridge.js:24
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: i18n.js (1130 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/314c1e30-cca6-4e01-9127-fa47eaf48c08/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/314c1e30-cca6-4e01-9127-fa47eaf48c08/

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.