← Back to scan
File as GitHub Issue repo: esengine/DeepSeek-Reasonix

Push this scan report to esengine/DeepSeek-Reasonix

Click the green button below to open GitHub’s new-issue form, pre-filled with the report title, summary table, top findings, and an embedded score-card image. No authentication needed — you review on GitHub before submitting. Repobility is credited as the scanner.

Embedded score card image

This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.

Repobility score card

Issue title

Duplicated implementation block across source files

Curate findings to include

Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.

Top 5 (default)
Severity Rule Title File:line
CRIT SEC002 [SEC002] Hardcoded API Key: Hardcoded API key found in source code. src/config.ts:213
MED AIC003 Duplicated implementation block across source files src/server/api/skills.ts:22
MED AIC003 Duplicated implementation block across source files src/server/api/project-tree.ts:7
MED AIC003 Duplicated implementation block across source files src/server/api/checkpoint-restore.ts:5
MED AIC003 Duplicated implementation block across source files src/mcp/types.ts:1
MED AIC003 Duplicated implementation block across source files src/mcp/streamable-http.ts:86
MED AIC003 Duplicated implementation block across source files src/cli/ui/prompt-viewport.ts:11
MED AIC003 Duplicated implementation block across source files src/cli/ui/ShellConfirm.tsx:147
MED AIC003 Duplicated implementation block across source files src/cli/ui/ReplayApp.tsx:16
MED AIC003 Duplicated implementation block across source files src/cli/ui/McpMarketplace.tsx:67
MED AIC003 Duplicated implementation block across source files src/cli/commands/run.ts:95
MED AIC003 Duplicated implementation block across source files scripts/perf/profile-tui-sync.tsx:3
MED AGT007 localStorage write failures are swallowed silently docs/src/i18n.jsx:25
MED AGT007 localStorage write failures are swallowed silently docs/i18n.js:386
MED AGT007 localStorage write failures are swallowed silently desktop/src/i18n/index.ts:45
MED AGT007 localStorage write failures are swallowed silently dashboard/src/panels/chat.ts:138
MED AGT007 localStorage write failures are swallowed silently dashboard/src/lib/i18n.ts:48
MED AGT007 localStorage write failures are swallowed silently dashboard/app.js:87
MED WEB003 Public web service has no security.txt .well-known/security.txt
MED WEB015 Public web app has no Content Security Policy index.html
MED AGT015 Remote install command pipes network code directly to a shell dashboard/src/panels/semantic.ts:463
MED AGT013 Agent auto-approve or skip-permissions mode is easy to enable src/cli/index.ts:370
MED AGT013 Agent auto-approve or skip-permissions mode is easy to enable CHANGELOG.md:122
MED SEC005 [SEC005] Command Injection Risk: Unsafe shell execution or eval of user input. src/cli/ui/slash/commands.ts:426
MED SEC005 [SEC005] Command Injection Risk: Unsafe shell execution or eval of user input. dashboard/src/panels/chat.ts:458
MED SEC005 [SEC005] Command Injection Risk: Unsafe shell execution or eval of user input. src/at-mentions.ts:364
MED ERR002 [ERR002] Empty Catch Block: Empty catch blocks hide errors. docs/src/config.jsx:305
MED ERR002 [ERR002] Empty Catch Block: Empty catch blocks hide errors. docs/src/install.jsx:6
MED ERR002 [ERR002] Empty Catch Block: Empty catch blocks hide errors. docs/src/community.jsx:18
LOW WEB008 Public docs site has no llms.txt llms.txt
LOW AIC002 Source file name looks like an AI patch artifact src/cli/ui/hooks/handle-assistant-final…:1
LOW WEB011 Public web app has no humans.txt humans.txt
Reset to top 5 32 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `esengine/DeepSeek-Reasonix`

**Score: 73/100 (B+)**  ·  42 findings  ·  scanned 2026-05-15 17:14 UTC  ·  138,535 LOC

| Severity | Count |
|---|---|
| CRITICAL | 1 |
| HIGH | 0 |
| MEDIUM | 28 |
| LOW | 3 |

📊 [Full filterable report](https://repobility.com/scan/a77898c5-f7a8-450e-b012-1fe5a360795f/)  ·  ![scorecard](https://repobility.com/scan/a77898c5-f7a8-450e-b012-1fe5a360795f/report.png?v=1778865240-s2)

### Top findings

1. **CRITICAL** `SEC002` — Hardcoded API Key
   `src/config.ts:213` · A07:2021 Identification & Authentication Failures
2. **MEDIUM** `AIC003` — Duplicated implementation block across source files
   `src/server/api/skills.ts:22`
3. **MEDIUM** `AIC003` — Duplicated implementation block across source files
   `src/server/api/project-tree.ts:7`
4. **MEDIUM** `AIC003` — Duplicated implementation block across source files
   `src/server/api/checkpoint-restore.ts:5`
5. **MEDIUM** `AIC003` — Duplicated implementation block across source files
   `src/mcp/types.ts:1`

---

**Security note**: this issue is public. If any flagged finding is a real, exploitable vulnerability, please redirect to your `SECURITY.md` policy or open a [private security advisory](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) instead. We're happy to close this and re-submit privately.

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/a77898c5-f7a8-450e-b012-1fe5a360795f/_
Megaproject â high spam risk
Could not determine 'esengine/DeepSeek-Reasonix' star count (GitHub API rate-limited or unreachable). When in doubt about repo size, prefer opening a focused PR or a discussion rather than an issue.
Already filed
14/42 findings (33%) on this scan are already flagged as test-file, won't-fix, or suppressed. The scan is too noisy to file as a single issue. Curate down to specific actionable findings, or address the FP source first.

The button opens GitHubâs new-issue page in a new tab. You will see the title + body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue" button. Repobility never posts anything on your behalf.

For real security findings on big repos: use the project's SECURITY.md or private advisory flow instead of a public issue.