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

vatsalmaniar/SSC_Inventory

https://github.com/vatsalmaniar/SSC_Inventory · scanned 2026-06-16 00:47 UTC (2 months, 1 week ago)

76 raw signals (0 security + 76 graph)

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

Complete repo analysis

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

JSON
Combined
68.1
/100
Security checks
68
0 findings
System graph
68
77.8% cov · 55 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 0 Medium 12 Low 30 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 55 Crowd 0 Layer: Frontend 6 Security 12 Cicd 1 Quality 36
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 68.1/100 with 77.8% coverage. It contains 1464 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 76 findings — concentrated in quality (57), security (12), frontend (6). Risk profile is low: 0 critical, 0 high, 33 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 42 of 55 actionable findings. 76 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.

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/pages/Login.jsx:393
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/lib/kpiFetchers.js:136
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: .claude/settings.local.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.
.claude/settings.local.json 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 license, ci, 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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, 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 22 occurrences Frontend route `/not-authorized` has no Link/navigate to it — src/App.jsx
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.
22 occurrences
repo-level (22 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/send-po-to-vendor/index.ts:11
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/send-po-to-vendor/index.ts:11 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/pages/Login.jsx:393
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/pages/Login.jsx:393 Dangerous innerhtml
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 329 placeholder/mock markers across 55 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 92 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — src/pages/CRMNewOpportunity.jsx:191
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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — src/pages/ForecastPOReviewModal.jsx:48
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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — src/pages/UserManagement.jsx:291
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 security security conf 1.00 Insecure pattern 'document_write' in src/pages/CRMOpportunityDetail.jsx:902
Found a known-risky pattern (document_write). Review and replace if possible.
src/pages/CRMOpportunityDetail.jsx:902 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in src/pages/CRMQuotations.jsx:407
Found a known-risky pattern (document_write). Review and replace if possible.
src/pages/CRMQuotations.jsx:407 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in src/pages/CustomerDetail.jsx:449
Found a known-risky pattern (document_write). Review and replace if possible.
src/pages/CustomerDetail.jsx:449 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in src/pages/FCOrderDetail.jsx:329
Found a known-risky pattern (document_write). Review and replace if possible.
src/pages/FCOrderDetail.jsx:329 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in src/pages/GRNDetail.jsx:382
Found a known-risky pattern (document_write). Review and replace if possible.
src/pages/GRNDetail.jsx:382 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in src/pages/OrderDetail.jsx:104
Found a known-risky pattern (document_write). Review and replace if possible.
src/pages/OrderDetail.jsx:104 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in src/pages/PurchaseInvoiceDetail.jsx:48
Found a known-risky pattern (document_write). Review and replace if possible.
src/pages/PurchaseInvoiceDetail.jsx:48 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in src/pages/PurchaseOrderDetail.jsx:931
Found a known-risky pattern (document_write). Review and replace if possible.
src/pages/PurchaseOrderDetail.jsx:931 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in src/pages/StockTransferDetail.jsx:198
Found a known-risky pattern (document_write). Review and replace if possible.
src/pages/StockTransferDetail.jsx:198 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in src/pages/VendorDetail.jsx:344
Found a known-risky pattern (document_write). Review and replace if possible.
src/pages/VendorDetail.jsx:344 Document write
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 `isOld` in src/pages/Accounts.jsx:401
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 React Flow <MiniMap> without dark background — src/pages/CRMFieldVisits.jsx:491
A bare <MiniMap> renders with the vendor's white default in dark themes. Wrap the canvas in a class that overrides `.react-flow__minimap` background, or pass an explicit `style`/`maskColor`/`bgColor`. Why: P1 in CHECKLIST.md — vendor defaults bleed light through. Rule id: fq.minimap.no-bg
Fq minimap no bg
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/pages/PurchaseOrderDetail.jsx:495
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 quality Complexity conf 1.00 Very large file: src/components/Layout.jsx (810 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/BillingOrderDetail.jsx (1380 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/CRMOpportunityDetail.jsx (2570 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/CustomerDetail.jsx (1324 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/FCOrderDetail.jsx (1284 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/GRNDetail.jsx (863 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/OrderDetail.jsx (2358 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/ProcurementForecast.jsx (1074 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/PurchaseInvoiceDetail.jsx (846 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/PurchaseOrderDetail.jsx (2305 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/VendorDetail.jsx (976 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/3bad18f4-f162-45d9-a549-2ebe2a8cbe44/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/3bad18f4-f162-45d9-a549-2ebe2a8cbe44/

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.