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

Yashpetkar7/Logistics-Problem-Sp-jain-Nova-

https://github.com/Yashpetkar7/Logistics-Problem-Sp-jain-Nova- · scanned 2026-06-16 01:04 UTC (2 months, 1 week ago)

18 raw signals (0 security + 18 graph)

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

Complete repo analysis

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

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

Showing 17 of 18 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/about.html:157
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/about.html:157 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin.html:245
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin.html:245 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/index.html:387
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/index.html:387 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/pass.html:446
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/pass.html:446 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/validator.html:146
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/validator.html:146 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in public/index.html:316
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
public/index.html:316 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in public/pass.html:341
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
public/pass.html:341 Local storage auth token
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 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
0 test file(s) for 2 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: 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 hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 11 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:4 containersPinned dependencies
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 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 — server.js:804
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/c4002d67-1f3d-44b6-a195-9ae0017c888f/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/c4002d67-1f3d-44b6-a195-9ae0017c888f/

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.