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

pradeeplodhi3001/cliphi-web-app

https://github.com/pradeeplodhi3001/cliphi-web-app · scanned 2026-09-03 07:51 UTC (1 week, 1 day ago)

34 raw signals (0 security + 34 graph)

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

Complete repo analysis

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

JSON
Combined
63.3
/100
Security checks
63
0 findings
System graph
63
70.0% cov · 34 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 3 Medium 7 Low 15 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 34 Crowd 0 Layer: Frontend 19 Quality 8 Security 7
Scan summary Repository scanned at 63.3/100 with 70.0% coverage. It contains 239 nodes across 1 cross-layer flows, written primarily in mixed languages. Engine surfaced 34 findings — concentrated in frontend (19), quality (8), security (7). Risk profile is high: 0 critical, 3 high, 7 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 24 of 34 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 Skillspector conf 0.70 SkillSpector SC6 (supply-chain) in package.json
next Package name closely resembles a popular package, suggesting possible typosquatting. Attackers publish malicious packages with similar names to trick developers into installing them. Skill: unknown Rule: SC6 Category: supply-chain Severity: HIGH Confidence: 0.70 Remediation: Verify the pa…
package.json:16 Mcp skillSupply chainSc6
high System graph security Skillspector conf 0.85 SkillSpector TM1 (tool-misuse) in package-lock.json
RMnFX7YQsMoh7lWfcM4NEHHymBX/ Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns). Skill: unknown Rule: TM1 Category: tool-misuse Severity: HIGH Confidence: 0.85 Remediation: …
package-lock.json:543 Mcp skillTool misuseTm1
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 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 33 placeholder/mock markers across 7 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 security Skillspector conf 0.60 SkillSpector E1 (data-exfil) in app/api/login/route.ts
fetch( "https://clipgen-nogo.onrender.com/auth", { method: "POST" Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended. Skill: unknown Rule: E1 Category: data-exfil Severity: MEDIUM Confidence: 0.60 Rem…
app/api/login/route.ts:7 Mcp skillData exfilE1
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
2 test file(s) for 39 source file(s) (ratio 0.05). Consider adding integration or unit tests for critical paths.
Coverage
low System graph frontend Frontend quality conf 0.85 Debug `console.log` remains in browser-facing code — app/components/GenerateButton.tsx:236
Remove debug output or route intentional diagnostics through the project's structured logger. Browser console output can expose state and create noise; server and CLI output are outside this rule's scope. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
app/components/GenerateButton.tsx:236 Fq console leak
low System graph frontend Frontend quality conf 0.85 Debug `console.log` remains in browser-facing code — app/components/Hero.tsx:388
Remove debug output or route intentional diagnostics through the project's structured logger. Browser console output can expose state and create noise; server and CLI output are outside this rule's scope. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
app/components/Hero.tsx:388 Fq console leak
low System graph frontend Frontend quality conf 0.85 Debug `console.log` remains in browser-facing code — app/components/LoginCard.tsx:25
Remove debug output or route intentional diagnostics through the project's structured logger. Browser console output can expose state and create noise; server and CLI output are outside this rule's scope. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
app/components/LoginCard.tsx:25 Fq console leak
low System graph frontend Frontend quality conf 0.85 Debug `console.log` remains in browser-facing code — app/components/tesxt.tsx:42
Remove debug output or route intentional diagnostics through the project's structured logger. Browser console output can expose state and create noise; server and CLI output are outside this rule's scope. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
app/components/tesxt.tsx:42 Fq console leak
low System graph frontend Frontend quality conf 0.85 Debug `console.log` remains in browser-facing code — app/dashboard/components/DashboardHeader.tsx:34
Remove debug output or route intentional diagnostics through the project's structured logger. Browser console output can expose state and create noise; server and CLI output are outside this rule's scope. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
app/dashboard/components/DashboardHeader.tsx:34 Fq console leak
low System graph frontend Frontend quality conf 0.85 Debug `console.log` remains in browser-facing code — app/dashboard/preview/page.tsx:115
Remove debug output or route intentional diagnostics through the project's structured logger. Browser console output can expose state and create noise; server and CLI output are outside this rule's scope. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
app/dashboard/preview/page.tsx:115 Fq console leak
low System graph frontend Frontend quality conf 0.85 Debug `console.log` remains in browser-facing code — app/dashboard/processing/page.tsx:136
Remove debug output or route intentional diagnostics through the project's structured logger. Browser console output can expose state and create noise; server and CLI output are outside this rule's scope. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
app/dashboard/processing/page.tsx:136 Fq console leak
low System graph frontend Frontend quality conf 0.85 Debug `console.log` remains in browser-facing code — app/dashboard/projects/page.tsx:185
Remove debug output or route intentional diagnostics through the project's structured logger. Browser console output can expose state and create noise; server and CLI output are outside this rule's scope. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
app/dashboard/projects/page.tsx:185 Fq console leak
low System graph frontend Frontend quality conf 0.85 Debug `console.log` remains in browser-facing code — app/login/page.tsx:124
Remove debug output or route intentional diagnostics through the project's structured logger. Browser console output can expose state and create noise; server and CLI output are outside this rule's scope. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
app/login/page.tsx:124 Fq console leak
low System graph frontend Frontend quality conf 0.85 Debug `console.log` remains in browser-facing code — app/sign-up/page.tsx:142
Remove debug output or route intentional diagnostics through the project's structured logger. Browser console output can expose state and create noise; server and CLI output are outside this rule's scope. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
app/sign-up/page.tsx:142 Fq console leak
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 56 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 0.85 Icon-only button without accessible name — app/components/LoginCard.tsx:63
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
app/components/LoginCard.tsx:63 Fq button no label
low System graph quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
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 security Skillspector conf 0.40 SkillSpector SC1 (supply-chain) in package.json
"@reduxjs/toolkit": "^2.12.0" Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions. Skill: unknown Rule: SC1 Category: supply-chain Severity: LOW Confidence: 0.40 Remediation: Pin all dependency versions in requirements.txt or pyproject.tom…
package.json:12 Mcp skillSupply chainSc1
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/90bd7d62-b84a-48ab-9c32-d4f2472ae525/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/90bd7d62-b84a-48ab-9c32-d4f2472ae525/

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.