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

qiaeru/couplecards

https://github.com/qiaeru/couplecards · scanned 2026-06-15 23:42 UTC (2 months, 4 weeks ago)

61 raw signals (0 security + 61 graph)

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

Complete repo analysis

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

JSON
Combined
61.5
/100
Security checks
62
0 findings
System graph
62
100.0% cov · 59 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 12 Medium 20 Low 14 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 59 Crowd 0 Layer: Hardware 2 Security 11 Cicd 2 Quality 22 Api 22
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 61.5/100 with 100.0% coverage. It contains 532 nodes across 29 cross-layer flows, written primarily in mixed languages. Engine surfaced 61 findings — concentrated in quality (22), api (22), security (11). Risk profile is high: 0 critical, 12 high, 20 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 46 of 59 actionable findings. 61 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 api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/users/${id} (public/js/features/admin/users.js:129)
`public/js/features/admin/users.js:129` calls `DELETE /api/admin/users/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/users/<p>` If this points at an external API, prefix it with `https://` so …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/cards/export (public/js/features/admin/deck-sync.js:22)
`public/js/features/admin/deck-sync.js:22` calls `GET /api/admin/cards/export` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/cards/export` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/users (public/js/features/admin/users.js:14)
`public/js/features/admin/users.js:14` calls `GET /api/admin/users` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/users` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /locales/${locale}.json (public/js/core/i18n.js:25)
`public/js/core/i18n.js:25` calls `GET /locales/${locale}.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/locales/<p>.json` 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 /views/${name}.html (public/js/core/router.js:28)
`public/js/core/router.js:28` calls `GET /views/${name}.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/views/<p>.html` 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: POST /api/admin/cards/import (public/js/features/admin/deck-sync.js:210)
`public/js/features/admin/deck-sync.js:210` calls `POST /api/admin/cards/import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/cards/import` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/cards/import (public/js/features/admin/deck-sync.js:243)
`public/js/features/admin/deck-sync.js:243` calls `POST /api/admin/cards/import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/cards/import` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/cards/sync (public/js/features/admin/deck-sync.js:121)
`public/js/features/admin/deck-sync.js:121` calls `POST /api/admin/cards/sync` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/cards/sync` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/cards/sync (public/js/features/admin/deck-sync.js:162)
`public/js/features/admin/deck-sync.js:162` calls `POST /api/admin/cards/sync` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/cards/sync` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/users (public/js/features/admin/users.js:102)
`public/js/features/admin/users.js:102` calls `POST /api/admin/users` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/users` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/users/${id}/reset-password (public/js/features/admin/users.js:115)
`public/js/features/admin/users.js:115` calls `POST /api/admin/users/${id}/reset-password` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/users/<p>/reset-password` If this points at an external API, p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/users/${id}/unlock (public/js/features/admin/users.js:135)
`public/js/features/admin/users.js:135` calls `POST /api/admin/users/${id}/unlock` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/users/<p>/unlock` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — public/js/core/i18n.js:25
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 — public/js/core/router.js:28
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 — public/js/features/admin/deck-sync.js:22
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 Tests conf 1.00 CI is configured but no tests are detected
A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.
CI/CDConfig theaterRepo hardening
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
docker/build-push-action@v7 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/release.yml:34 CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 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.
.github/workflows/release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/core/router.js:71
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/core/router.js:71 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/features/admin/cards.js:50
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/features/admin/cards.js:50 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/features/admin/deck-sync.js:167
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/features/admin/deck-sync.js:167 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/features/admin/users.js:26
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/features/admin/users.js:26 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/features/collection/collection.js:106
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/features/collection/collection.js:106 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/features/deck/draw.js:36
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/features/deck/draw.js:36 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/features/history/history.js:48
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/features/history/history.js:48 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/features/settings/settings.js:138
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/features/settings/settings.js:138 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/ui/password-strength.js:54
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/ui/password-strength.js:54 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/ui/shell.js:154
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/ui/shell.js:154 Direct innerhtml assignment
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 quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 12 placeholder/mock markers across 4 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 54 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 7 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `DATA_DIR`, `DATA_SEED_DIR`, `DB_PATH`, `HOST`, `LANG`, `NODE_ENV`, `PUBLIC_DIR`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
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 hardware Supply chain conf 1.00 3 occurrences Docker base image is tag-pinned but not digest-pinned: node:24-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 10, 16, 25
Dockerfile:10, 16, 25 (3 hits)
containersPinned dependencies
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 api Wiring conf 1.00 Unused endpoint: DELETE /users/:id
`server/src/routes/users.js` declares `DELETE /users/: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: GET /cards/export
`server/src/routes/admin-cards.js` declares `GET /cards/export` 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: GET /manifest.webmanifest
`server/src/routes/manifest.js` declares `GET /manifest.webmanifest` 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: GET /users
`server/src/routes/users.js` declares `GET /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: PATCH /users/:id
`server/src/routes/users.js` declares `PATCH /users/: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: POST /cards/import
`server/src/routes/admin-cards.js` declares `POST /cards/import` 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: POST /cards/sync
`server/src/routes/admin-cards.js` declares `POST /cards/sync` 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: POST /users
`server/src/routes/users.js` declares `POST /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: POST /users/:id/reset-password
`server/src/routes/users.js` declares `POST /users/:id/reset-password` 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: POST /users/:id/unlock
`server/src/routes/users.js` declares `POST /users/:id/unlock` 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
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/a0d0eabd-7d04-418c-add5-ff21d5be24c2/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a0d0eabd-7d04-418c-add5-ff21d5be24c2/

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.