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.

wordyappteam/wordy

https://github.com/wordyappteam/wordy · scanned 2026-06-16 00:59 UTC (2 months, 1 week ago)

42 raw signals (0 security + 42 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 41 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 3 Medium 16 Low 13 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 41 Crowd 0 Layer: Frontend 12 Data 1 Security 6 Cicd 1 Quality 17 Api 4

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 88.9% coverage. It contains 492 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 42 findings — concentrated in quality (18), frontend (12), security (6). Risk profile is high: 0 critical, 3 high, 17 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 32 of 41 actionable findings. 42 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: POST https://api.anthropic.com/v1/messages (api/anthropic.js:12)

`api/anthropic.js:12` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an external API, prefix it with `https:…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (netlify/functions/anthropic.js:13)

`netlify/functions/anthropic.js:13` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an external API, prefix i…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (vite.config.js:27)

`vite.config.js:27` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an external API, prefix it with `https://…

Dangling fetchFetch

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/pages/Chat.jsx:377

Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html

Fq dangerous html

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/launch.json

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/launch.json VerificationClaude instruction

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, tests. 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, tests. 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 quality Integrity conf 1.00 2 occurrences Frontend route `/multiple-choice` has no Link/navigate to it — src/App.jsx

The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.

2 occurrences

repo-level (2 hits)

Orphan pageWiring

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in vite.config.js:11

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

vite.config.js:11 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/pages/Chat.jsx:377

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

src/pages/Chat.jsx:377 Dangerous innerhtml

medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in src/lib/sessionFlow.js:21

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

src/lib/sessionFlow.js:21 Local storage auth token

medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in src/pages/Dashboard.jsx:409

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

src/pages/Dashboard.jsx:409 Local storage auth token

medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in src/pages/Session.jsx:53

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

src/pages/Session.jsx:53 Local storage auth token

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 data Coverage conf 1.00 ORM models found but no DB engine detected

The repo defines tables/models but no DB connection string was found. Likely lives in env vars or a config file the scanner didn't read.

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 35 placeholder/mock markers across 10 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 39 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — src/pages/Dictionary.jsx:2386

A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…

Fq active light bg

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

Found 6 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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — src/pages/Chat.jsx:1223

A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label

Fq button no label

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — src/pages/Dictionary.jsx:566

Fq button no label

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — src/pages/Reader.jsx:204

Fq button no label

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 `wordsNeedingLegacy` in src/pages/WordOrder.jsx:107

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 — src/lib/AuthContext.jsx:42

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 — src/lib/claude.js:181

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 api Wiring conf 1.00 Unused endpoint: USE /api/anthropic/v1/messages

`vite.config.js` declares `USE /api/anthropic/v1/messages` 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: src/pages/Chat.jsx (1372 lines)

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

low System graph quality Complexity conf 1.00 Very large file: src/pages/Dictionary.jsx (2599 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/04f8d10a-0a7e-468f-8deb-7b0cc414777e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/04f8d10a-0a7e-468f-8deb-7b0cc414777e/

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.