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

silentganja/VibeGuard

https://github.com/silentganja/VibeGuard · scanned 2026-06-16 00:12 UTC (2 months, 2 weeks ago)

24 raw signals (0 security + 24 graph)

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

Complete repo analysis

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

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

Showing 22 of 24 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 'eval_used' in src/infrastructure/llm.ts:134
Found a known-risky pattern (eval_used). Review and replace if possible.
src/infrastructure/llm.ts:134 Eval used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in src/infrastructure/llm.ts:134
Found a known-risky pattern (exec_used). Review and replace if possible.
src/infrastructure/llm.ts:134 Exec used
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/engine/healer.ts:79
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/engine/exporter.ts:213
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 security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/engine/healer.ts:79
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/engine/healer.ts:79 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/build.mjs:28
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/build.mjs:28 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/verify.mjs:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/verify.mjs:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/analyzer/git.ts:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/analyzer/git.ts:17 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/compliance/compliance.ts:25
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/compliance/compliance.ts:25 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/engine/exporter.ts:19
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/engine/exporter.ts:19 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/engine/runner.ts:24
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/engine/runner.ts:24 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/infrastructure/checker.ts:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/infrastructure/checker.ts:17 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/infrastructure/dbGuard.ts:26
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/infrastructure/dbGuard.ts:26 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 Tests conf 1.00 Very low test-to-source ratio
1 test file(s) for 35 source file(s) (ratio 0.03). 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: license, ci. 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 41 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 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 `binary_copy` in src/core/types.ts:380
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 Integrity conf 1.00 Old/deprecated-named symbol `binary_copy` in src/infrastructure/dbGuard.ts:146
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 cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
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
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/e1bbebcd-9aac-4756-b405-d2ffa0d9e7f6/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/e1bbebcd-9aac-4756-b405-d2ffa0d9e7f6/

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.