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.

Wick-Lim/helper

https://github.com/Wick-Lim/helper · scanned 2026-06-16 00:57 UTC (2 months, 1 week ago)

44 raw signals (0 security + 44 graph)

File as issue Image

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. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 44 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 14 Medium 13 Low 14 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 44 Crowd 0 Layer: Frontend 6 Hardware 5 Security 5 Cicd 1 Quality 14 Api 13

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 68.1/100 with 100.0% coverage. It contains 372 nodes across 7 cross-layer flows, written primarily in mixed languages. Engine surfaced 44 findings — concentrated in quality (14), api (13), frontend (6). Risk profile is high: 0 critical, 14 high, 13 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 41 of 44 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/conversations?limit=50&offset=${historyOffset}&sessionId=web-session (src/webui/app.js:141)

`src/webui/app.js:141` calls `GET /api/conversations?limit=50&offset=${historyOffset}&sessionId=web-session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/conversations` If this points at an external API, prefix it…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/conversations?limit=50&offset=0&sessionId=web-session (src/webui/app.js:113)

`src/webui/app.js:113` calls `GET /api/conversations?limit=50&offset=0&sessionId=web-session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/conversations` If this points at an external API, prefix it with `https://…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/files?dir=${encodeURIComponent(filesDir)} (src/webui/app.js:741)

`src/webui/app.js:741` calls `GET /api/files?dir=${encodeURIComponent(filesDir)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/files` If this points at an external API, prefix it with `https://` so the matcher ski…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/health (src/webui/app.js:44)

`src/webui/app.js:44` calls `GET /api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/health` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/memory (src/webui/app.js:585)

`src/webui/app.js:585` calls `GET /api/memory` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/memory` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/stats (src/webui/app.js:952)

`src/webui/app.js:952` calls `GET /api/stats` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stats` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/tasks/${id} (src/webui/app.js:840)

`src/webui/app.js:840` calls `GET /api/tasks/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/tasks/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/tasks?limit=30&offset=${tasksOffset} (src/webui/app.js:685)

`src/webui/app.js:685` calls `GET /api/tasks?limit=30&offset=${tasksOffset}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/tasks` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/tasks?limit=30&offset=0 (src/webui/app.js:625)

`src/webui/app.js:625` calls `GET /api/tasks?limit=30&offset=0` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/tasks` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/thoughts?limit=20&offset=${thoughtsOffset} (src/webui/app.js:551)

`src/webui/app.js:551` calls `GET /api/thoughts?limit=20&offset=${thoughtsOffset}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/thoughts` If this points at an external API, prefix it with `https://` so the matcher…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/thoughts?limit=20&offset=0 (src/webui/app.js:491)

`src/webui/app.js:491` calls `GET /api/thoughts?limit=20&offset=0` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/thoughts` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/timeline?limit=30&offset=${timelineOffset} (src/webui/app.js:379)

`src/webui/app.js:379` calls `GET /api/timeline?limit=30&offset=${timelineOffset}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/timeline` If this points at an external API, prefix it with `https://` so the matcher…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/timeline?limit=30&offset=0 (src/webui/app.js:310)

`src/webui/app.js:310` calls `GET /api/timeline?limit=30&offset=0` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/timeline` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph hardware Supply chain conf 1.00 Dockerfile pipes a remote installer into a shell

Executing downloaded code during image build gives the remote endpoint build-time code execution. Prefer pinned packages or verify downloaded installers by checksum/signature.

Dockerfile:32 containersRemote installer

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/api/server.ts:129

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 — src/llm/local.ts:181

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 — src/telegram/bot.ts:111

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 — src/tools/web.ts:196

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 hardware Security conf 1.00 Dockerfile runs as root: Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in src/api/routes.ts:436

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

src/api/routes.ts:436 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in src/api/server.ts:14

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

src/api/server.ts:14 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/webui/app.js:172

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

src/webui/app.js:172 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in src/webui/app.js:386

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

src/webui/app.js:386 Insert adjacent html

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 Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 12 placeholder/mock markers across 3 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

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 hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found

Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.

Deployment

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

Found 27 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: debian:bookworm-slim

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

Dockerfile:2 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: oven/bun:1-debian

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

Dockerfile:16 containersPinned dependencies

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

8 tests / 43 src (ratio 0.19).

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 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 — src/agent/planner.ts:30