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

qwwiwi/dashi-plugin-claude-code

https://github.com/qwwiwi/dashi-plugin-claude-code · scanned 2026-06-15 23:44 UTC (2 months, 4 weeks ago)

142 raw signals (0 security + 142 graph)

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

Complete repo analysis

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

JSON
Combined
67.3
/100
Security checks
67
0 findings
System graph
67
88.9% cov · 142 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 13 Low 14 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 142 Crowd 0 Layer: Frontend 1 Network 2 Security 6 Cicd 1 Quality 132
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 67.3/100 with 88.9% coverage. It contains 1506 nodes across 4 cross-layer flows, written primarily in mixed languages. Engine surfaced 142 findings — concentrated in quality (132), security (6), network (2). Risk profile is high: 1 critical, 1 high, 13 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 28 of 142 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 security security conf 1.00 Insecure pattern 'exec_used' in plugin/src/commands/keys.ts:178
Found a known-risky pattern (exec_used). Review and replace if possible.
plugin/src/commands/keys.ts:178 Exec used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — plugin/src/channel/tools.ts:191
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 authority lacks a verifier contract: plugin/.mcp.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.
plugin/.mcp.json VerificationMcp config
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: plugin/CLAUDE.md
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.
plugin/CLAUDE.md 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 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 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 security security conf 1.00 Insecure pattern 'node_child_process' in plugin/src/commands/keys.ts:25
Found a known-risky pattern (node_child_process). Review and replace if possible.
plugin/src/commands/keys.ts:25 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in plugin/src/server.ts:19
Found a known-risky pattern (node_child_process). Review and replace if possible.
plugin/src/server.ts:19 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in plugin/src/status/tmux-mirror.ts:32
Found a known-risky pattern (node_child_process). Review and replace if possible.
plugin/src/status/tmux-mirror.ts:32 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in skills/doctor-dashi-plugin/scripts/doctor.ts:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
skills/doctor-dashi-plugin/scripts/doctor.ts:17 Node child process
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 25 placeholder/mock markers across 11 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 network Security conf 1.00 Privileged port 11 in use
Port 11 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
docs/dev/goals/gateway-parity-migration/state.yaml Ports
medium System graph network Security conf 1.00 Privileged port 54 in use
Port 54 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
docs/dev/goals/gateway-parity-migration/state.yaml Ports
low System graph quality Integrity conf 1.00 41 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CHAT_ID`, `CLAUDE_BIN`, `CLAUDE_BINARY_PATH`, `CLAUDE_WORKSPACE_DIR`, `GROQ_API_KEY`, `INVOCATION_TIMEOUT_SEC`, `LOG_LEVEL`, `MULTICHAT_STATE_DIR` + 33 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: ci, lockfile. 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 quality Debug conf 1.00 Debug logging residue appears in source files
Found 12 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 quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: plugin/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.
plugin/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `uOld` in plugin/tests/hooks/fallback-reply-hook.test.ts:124
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 quality Complexity conf 1.00 Very large file: plugin/src/security/permission-policy.ts (1776 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: plugin/src/server.ts (1287 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: plugin/src/status/status-manager.ts (1339 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: plugin/src/telegram/handlers.ts (1370 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: plugin/src/webhook/server.ts (1666 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: plugin/tests/telegram/handlers.album.test.ts (1447 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: skills/doctor-dashi-plugin/scripts/doctor.test.ts (1305 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: skills/doctor-dashi-plugin/scripts/doctor.ts (2250 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/78446541-8ab4-452d-b8c7-6f7f373a31ab/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/78446541-8ab4-452d-b8c7-6f7f373a31ab/

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.