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

appleweiping/AIDE_DEV

https://github.com/appleweiping/AIDE_DEV · scanned 2026-06-17 01:34 UTC (1 month, 2 weeks ago)

53 raw signals (0 security + 53 graph)

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

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ +9.3 (diff) · 53 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

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

Showing 38 of 53 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 packages/core/src/git/operations.ts:7
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/core/src/git/operations.ts:7 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/core/src/safety/docker-sandbox.ts:75
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/core/src/safety/docker-sandbox.ts:75 Exec used
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — packages/desktop/src/components/Chat.tsx:132
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 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
softprops/action-gh-release@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/release.yml:48 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 'cors_wildcard' in packages/core/src/a2a/server.ts:103
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
packages/core/src/a2a/server.ts:103 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in packages/desktop/src/components/Chat.tsx:132
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
packages/desktop/src/components/Chat.tsx:132 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/vscode/src/chat-panel.ts:524
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/vscode/src/chat-panel.ts:524 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/core/src/context-loader.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/core/src/context-loader.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/core/src/git/operations.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/core/src/git/operations.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/core/src/hooks/manager.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/core/src/hooks/manager.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/core/src/mcp/client.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/core/src/mcp/client.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/core/src/safety/docker-sandbox.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/core/src/safety/docker-sandbox.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/core/src/tools/bash.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/core/src/tools/bash.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/core/src/tools/grep.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/core/src/tools/grep.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/core/src/tools/lsp.ts:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/core/src/tools/lsp.ts:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/core/src/tools/monitor.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/core/src/tools/monitor.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/core/src/tools/powershell.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/core/src/tools/powershell.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/core/src/tools/voice.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/core/src/tools/voice.ts:12 Node child process
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 39 placeholder/mock markers across 14 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 126 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: tests, 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 40 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 — packages/desktop/src/components/McpManager.tsx:249
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 quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/cli/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.
packages/cli/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/core/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.
packages/core/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/desktop/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.
packages/desktop/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/mobile/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.
packages/mobile/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/relay/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.
packages/relay/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/shared/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.
packages/shared/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/vscode/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.
packages/vscode/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `startOld` in packages/desktop/src/components/DiffViewer.tsx:15
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/cli/src/repl.ts:64
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 — packages/core/src/telemetry/index.ts:122
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 — packages/relay/src/index.ts:127
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
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/d920f6f8-ef2e-4bb0-95c6-bad0dd44cb05/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/d920f6f8-ef2e-4bb0-95c6-bad0dd44cb05/

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.