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

sapths/Navigate.io

https://github.com/sapths/Navigate.io · scanned 2026-06-16 00:02 UTC (2 months, 3 weeks ago)

192 raw signals (0 security + 192 graph)

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

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 176 actionable findings from 1 signal source. 16 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
64.1
/100
Security checks
64
0 findings
System graph
64
77.8% cov · 176 findings
Critical
22
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 22 High 1 Medium 19 Low 12 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 176 Crowd 0 Layer: Frontend 22 Security 29 Cicd 1 Quality 124
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 64.1/100 with 77.8% coverage. It contains 1192 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 192 findings — concentrated in quality (137), security (31), frontend (22). Risk profile is high: 24 critical, 1 high, 32 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 40 of 176 actionable findings. 192 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical System graph security Secrets conf 1.00 Possible secret in scripts/capture-landing-shots.mjs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/capture-landing-shots.mjs:24
critical System graph security Secrets conf 1.00 Possible secret in scripts/capture-pitch-screenshots.mjs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/capture-pitch-screenshots.mjs:22
critical System graph security Secrets conf 1.00 Possible secret in scripts/create-demo-user.mjs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/create-demo-user.mjs:68
critical System graph security Secrets conf 1.00 Possible secret in scripts/create-sales-owners.mjs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/create-sales-owners.mjs:139
critical System graph security Secrets conf 1.00 Possible secret in scripts/seed-mock-hierarchy.mjs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/seed-mock-hierarchy.mjs:70
critical System graph security Secrets conf 1.00 Possible secret in scripts/seed-mock-team.mjs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/seed-mock-team.mjs:93
critical System graph security Secrets conf 1.00 Possible secret in scripts/trigger-and-read-debug.mjs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/trigger-and-read-debug.mjs:26
critical System graph security Secrets conf 1.00 Possible secret in src/lib/godMode.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
src/lib/godMode.ts:35
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/skills/verify-backend-change.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/skills/verify-backend-change.md:76 SecretsClaude instruction
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/test-dev-logs.mjs:57
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/test-github-webhook.mjs:86
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/test-vercel-webhook.mjs:77
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — supabase/functions/claude-proxy/index.ts:486
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — supabase/functions/dev-logs/index.ts:134
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — supabase/functions/news-classifier/index.ts:6
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — supabase/functions/news-rss-poller/index.ts:20
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 instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, tests, operator-readme. 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 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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, tests, operator-readme. 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 quality Integrity conf 1.00 14 occurrences Frontend route `/login` has no Link/navigate to it — src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
14 occurrences
repo-level (14 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/claude-proxy/index.ts:617
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/claude-proxy/index.ts:617 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/dev-logs/index.ts:48
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/dev-logs/index.ts:48 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/news-classifier/index.ts:332
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/news-classifier/index.ts:332 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/news-fetch/index.ts:210
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/news-fetch/index.ts:210 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/news-rss-poller/index.ts:356
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/news-rss-poller/index.ts:356 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in happnnow_prototype.html:1530
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
happnnow_prototype.html:1530 Direct innerhtml assignment
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 323 placeholder/mock markers across 53 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — src/components/LoginPanel.tsx:411
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 457 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 cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 20, 23
.github/workflows/ci.yml:20, 23 (2 hits)
CI/CD securitySupply chainGithub actions
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 Docs conf 1.00 No README detected
No README file was found. Generated repos without README context are hard to operate, validate, or safely hand off.
ReadmeRepo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `companyByLegacy` in scripts/import-supabase.mjs:216
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: src/screens/admin/AdminDashboard.tsx (1578 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/screens/admin/CompanyManager.tsx (2782 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/screens/salesperson/Companies.tsx (1335 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/screens/salesperson/MyOrg.tsx (1231 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/screens/Settings.tsx (1385 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/c674619a-91ac-4dea-8694-be78af458f5c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/c674619a-91ac-4dea-8694-be78af458f5c/

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.