[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-83253":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":9,"totalLinesOfCode":9,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":9,"subscribersCount":16,"size":16,"stars1d":14,"stars7d":17,"stars30d":17,"stars90d":16,"forks30d":16,"starsTrendScore":17,"compositeScore":18,"rankGlobal":9,"rankLanguage":9,"license":9,"archived":19,"fork":19,"defaultBranch":20,"hasWiki":19,"hasPages":19,"topics":9,"createdAt":9,"pushedAt":9,"updatedAt":21,"readmeContent":22,"aiSummary":23,"trendingCount":16,"starSnapshotCount":16,"syncStatus":24,"lastSyncTime":25,"discoverSource":26},83253,"nyay-setu-working","viru0909-dev\u002Fnyay-setu-working","viru0909-dev","Digitalization of Judiciary System  ",null,"https:\u002F\u002Fgithub.com\u002Fviru0909-dev\u002Fnyay-setu-working","JavaScript",88,352,1,341,0,3,48.44,false,"main","2026-06-12 04:01:40","\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fbanner.png\" alt=\"Nyay Setu — Digital Judiciary Platform for India\" width=\"100%\" \u002F>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Ca href=\"https:\u002F\u002Fnyaysetu-lovat.vercel.app\u002F\">\n    \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLive%20Demo-nyaysetu.vercel.app-6C63FF?style=for-the-badge\" alt=\"Live Demo\" \u002F>\n  \u003C\u002Fa>\n   \n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fviru0909-dev\u002Fnyay-setu-working\u002Fissues\">\n    \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fissues\u002Fviru0909-dev\u002Fnyay-setu-working?style=for-the-badge&color=E05C5C\" alt=\"Open Issues\" \u002F>\n  \u003C\u002Fa>\n   \n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fviru0909-dev\u002Fnyay-setu-working\u002Fpulls\">\n    \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fissues-pr\u002Fviru0909-dev\u002Fnyay-setu-working?style=for-the-badge&color=43A047\" alt=\"Pull Requests\" \u002F>\n  \u003C\u002Fa>\n   \n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fviru0909-dev\u002Fnyay-setu-working\u002Fstargazers\">\n    \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fstars\u002Fviru0909-dev\u002Fnyay-setu-working?style=for-the-badge&color=FFB300\" alt=\"Stars\" \u002F>\n  \u003C\u002Fa>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cem>Democratizing Access to Justice Through Artificial Intelligence\u003C\u002Fem>\n\u003C\u002Fp>\n\n\u003Chr\u002F>\n\n> **Mission Statement**\n>\n> India has over 50 million pending court cases. Millions of citizens cannot afford legal counsel. Nyay Setu bridges this gap by putting an AI-powered legal assistant, end-to-end case management, and secure virtual courts in the hands of every Indian — entirely free of charge.\n\n\u003Chr\u002F>\n\n## Table of Contents\n\n- [Why Nyay Setu?](#why-nyay-setu)\n- [Key Features](#key-features)\n- [Tech Stack](#tech-stack)\n- [System Architecture & Data Flow](#system-architecture--data-flow)\n- [Quick Start](#quick-start)\n- [Documentation](#documentation)\n- [Contributing](#contributing)\n- [Contributors](#contributors)\n- [License](#license)\n\n\u003Chr\u002F>\n\n## Why Nyay Setu?\n\nThe Indian judiciary faces a systemic crisis that affects hundreds of millions of citizens:\n\n| Problem | Scale |\n|---|---|\n| Pending court cases | **50+ Million** |\n| Average time to resolve a civil case | **10–15 Years** |\n| Citizens unable to afford legal representation | **Hundreds of Millions** |\n\nNyay Setu is built to address this directly. The platform removes the three biggest barriers to legal access — cost, complexity, and distance — by digitizing the entire judiciary workflow and placing an AI legal assistant at every citizen's fingertips.\n\n\u003Chr\u002F>\n\n## Key Features\n\n**AI Legal Assistant (Vakil Friend)**\nA conversational AI companion powered by Groq's Llama 3.1 that helps citizens understand their legal rights, navigate case filings, review documents, and get real-time answers in plain, accessible language.\n\n**Role-Based Dashboards**\nSecure, tailored portals for every user type in the legal ecosystem: Litigants, Lawyers, Judges, Police, and Administrators — each with a workflow designed around their specific responsibilities.\n\n**End-to-End Case Management**\nFull case lifecycle support from initial filing to final order, including a case diary, hearing timelines, document management, and status tracking.\n\n**Evidence Vault**\nStructured digital evidence uploads with SHA-256 hash verification, creating a tamper-proof and legally admissible record for every case.\n\n**Digital FIR Handling**\nPolice can upload FIRs digitally. The AI instantly generates a structured summary and draft charge sheet, significantly reducing manual paperwork and processing time.\n\n**Virtual Courtrooms**\nNative WebRTC-based video conferencing integrated directly into the case timeline for secure, seamless remote hearings — no third-party applications required.\n\n**Secure Authentication**\nJWT-based stateless authentication with Spring Security, role-based access control, and multi-layer request filtering.\n\n\u003Chr\u002F>\n\n## Tech Stack\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FReact-20232A?style=for-the-badge&logo=react&logoColor=61DAFB\" \u002F>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FVite-646CFF?style=for-the-badge&logo=vite&logoColor=white\" \u002F>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FZustand-000000?style=for-the-badge&logo=react&logoColor=white\" \u002F>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FTailwindCSS-06B6D4?style=for-the-badge&logo=tailwindcss&logoColor=white\" \u002F>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FSpring%20Boot-6DB33F?style=for-the-badge&logo=springboot&logoColor=white\" \u002F>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FJava%2017-007396?style=for-the-badge&logo=openjdk&logoColor=white\" \u002F>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FPostgreSQL-4169E1?style=for-the-badge&logo=postgresql&logoColor=white\" \u002F>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FGroq%20Llama%203.1-FF6B35?style=for-the-badge&logo=meta&logoColor=white\" \u002F>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FOllama-000000?style=for-the-badge&logo=ollama&logoColor=white\" \u002F>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FWebRTC-333333?style=for-the-badge&logo=webrtc&logoColor=white\" \u002F>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FDocker-2496ED?style=for-the-badge&logo=docker&logoColor=white\" \u002F>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FGitHub%20Actions-2088FF?style=for-the-badge&logo=githubactions&logoColor=white\" \u002F>\n\u003C\u002Fp>\n\n\u003Chr\u002F>\n\n## Project Structure\n\n```text\nnyay-setu-working\u002F\n│\n├── frontend\u002F                        # React + Vite frontend application\n│   └── nyaysetu-frontend\u002F           # Main frontend source code\n│       ├── src\u002F\n│       │   ├── components\u002F          # Reusable UI components\n│       │   ├── pages\u002F               # Application pages\u002Froutes\n│       │   ├── services\u002F            # API service handlers\n│       │   ├── hooks\u002F               # Custom React hooks\n│       │   ├── store\u002F               # Zustand\u002Fglobal state management\n│       │   ├── utils\u002F               # Helper and utility functions\n│       │   └── assets\u002F              # Images, icons, and static assets\n│       ├── public\u002F                  # Public static files\n│       └── package.json             # Frontend dependencies and scripts\n│\n├── backend\u002F                         # Spring Boot backend services\n│   └── nyaysetu-backend\u002F\n│       ├── src\u002Fmain\u002Fjava\u002F           # Main backend application source\n│       ├── src\u002Fmain\u002Fresources\u002F      # Configuration files and resources\n│       ├── src\u002Ftest\u002F                # Backend test cases\n│       └── pom.xml                  # Maven configuration\n│\n├── nlp-orchestrator\u002F                # FastAPI-based NLP orchestration service\n│   ├── main.py                      # Main FastAPI application entry point\n│   ├── services\u002F                    # NLP and AI processing services\n│   ├── routes\u002F                      # API route handlers\n│   ├── models\u002F                      # AI\u002FNLP models and schemas\n│   └── requirements.txt             # Python dependencies\n│\n├── docs\u002F                            # Project documentation\n│   ├── architecture\u002F                # Architecture and system design docs\n│   ├── setup.md                     # Setup and installation guide\n│   └── additional-guides\u002F           # Supporting documentation\n│\n├── assets\u002F                          # README banners, screenshots, and assets\n│\n├── .github\u002F                         # GitHub workflows and community files\n│   ├── workflows\u002F                   # CI\u002FCD GitHub Actions workflows\n│   └── ISSUE_TEMPLATE\u002F              # GitHub issue templates\n│\n├── CONTRIBUTING.md                  # Contribution guidelines\n├── README.md                        # Main project documentation\n├── LICENSE                          # Open-source license\n└── SYSTEM_DOCUMENTATION.md          # API and system documentation\n```\n\n### Directory Overview\n\n| Directory | Purpose |\n|---|---|\n| `frontend\u002F` | Contains the React frontend application and UI components |\n| `backend\u002F` | Handles APIs, authentication, database access, and business logic |\n| `nlp-orchestrator\u002F` | Manages AI-powered legal assistance and NLP workflows |\n| `docs\u002F` | Contains setup guides, architecture diagrams, and technical documentation |\n| `assets\u002F` | Stores README images, banners, and other static assets |\n| `.github\u002F` | GitHub workflows, templates, and repository automation |\n\n## System Architecture & Data Flow\n\nNyay Setu's architecture is a microservices ecosystem structured into three tiers:\n1. **Frontend Tier (React + Vite)**: Renders role-based interactive dashboards, provides client-side WebRTC capabilities for virtual hearings, handles audio recording via browser APIs, and features a dynamic 3D Hologram Avatar component.\n2. **Core Backend Tier (Spring Boot)**: Manages case creation, secure session handling, user credentials, document verification vaults (SHA-256 hashed), Bhashini Indic language services integration, and routes conversational requests.\n3. **NLP & AI Tier (FastAPI)**: Coordinates advanced legal reasoning pipelines, decompiles multi-part queries, executes parallel web research on Indian Kanoon databases, synthesizes citations, and converts final summaries to Hinglish dialogue.\n\n### High-Level Service Communication\n\nThe following diagram shows the primary communication flow between the Frontend, Spring Boot Backend, and Python NLP services.\n\n```mermaid\nflowchart LR\n\n    User[User]\n\n    Frontend[React + Vite Frontend]\n\n    Backend[Spring Boot Backend]\n\n    NLP[NLP Orchestrator\u003Cbr\u002F>FastAPI]\n\n    LawGPT[LawGPT Service\u003Cbr\u002F>RAG Engine]\n\n    DB[(PostgreSQL)]\n\n    Groq[Groq API]\n    Gemini[Gemini API]\n\n    User --> Frontend\n\n    Frontend --> Backend\n\n    Backend --> DB\n\n    Backend --> NLP\n\n    Backend --> LawGPT\n\n    NLP --> Groq\n    NLP --> Gemini\n\n    LawGPT --> Groq\n```\n\n**Flow Overview**\n\n1. Users interact with the React frontend.\n2. Requests are routed to the Spring Boot backend.\n3. The backend manages authentication, case records, and database operations.\n4. AI-related requests are forwarded to the Python NLP Orchestrator.\n5. Legal knowledge retrieval is handled through the LawGPT RAG service.\n6. The NLP services communicate with external AI providers such as Groq and Gemini to generate responses.\n\n### Component Architecture & Interactions\n\n```mermaid\ngraph TD\n    %% Define Nodes\n    subgraph FrontendApp [Frontend Tier: React \u002F Vite]\n        UI[User Dashboard & Chat UI]\n        AV[3D Hologram Avatar]\n        RTC[WebRTC Client]\n    end\n\n    subgraph BackendApp [Backend Tier: Spring Boot]\n        Auth[Security & JWT filter]\n        VF_Svc[Vakil Friend Service]\n        Doc_Svc[Evidence Vault Service]\n        Bhash_Svc[Bhashini Translation API Client]\n        RAG_Proxy[RAG Proxy Client]\n    end\n\n    subgraph NLP_AI [NLP & AI Tier: Python \u002F FastAPI]\n        NLP_Orch[NLP Orchestrator: Port 8001]\n        L_GPT[LawGPT Service: Port 8001]\n        FAISS[(FAISS Vector Database)]\n    end\n\n    subgraph DatabaseTier [Data & Storage Tier]\n        DB[(PostgreSQL Database)]\n        Vault[Tamper-Proof Storage]\n    end\n\n    subgraph ExtAPIs [External Integrations]\n        Groq[Groq API: Llama 3.1 & 3.3]\n        Gemini[Google Gemini API: 1.5 Flash]\n        Kanoon[Indian Kanoon API]\n        Bhashini[Bhashini National Translation Service]\n        Ollama[Local Ollama: llama3\u002Fgemma3]\n    end\n\n    %% Interactions\n    UI -->|1. REST Request \u002F Auth| Auth\n    UI -->|2. Direct SSE Stream \u002Fresearch\u002Fdeep| NLP_Orch\n    AV -->|Lip-Sync Animation| UI\n\n    Auth --> VF_Svc\n    VF_Svc -->|Save sessions \u002F Case diary| DB\n    Doc_Svc -->|Write metadata \u002F SHA-256 hash| DB\n    Doc_Svc -->|Tamper-proof evidence| Vault\n\n    VF_Svc -->|Retrieve legal context| RAG_Proxy\n    RAG_Proxy -->|POST \u002Fcontext| L_GPT\n    L_GPT -->|FAISS Semantic Index Lookup| FAISS\n\n    VF_Svc -->|Translate to Indic \u002F ASR| Bhash_Svc\n    Bhash_Svc -->|Direct HTTP POST| Bhashini\n\n    VF_Svc -->|Llama-3.1 Chat Completion \u002F Fallback| Groq\n    VF_Svc -->|Local AI Fallback| Ollama\n    \n    NLP_Orch -->|Decompose & Route| Groq\n    NLP_Orch -->|Deep Reasoning| Gemini\n    NLP_Orch -->|Search Judgments| Kanoon\n    NLP_Orch -->|Hinglish Dialogue Translation| Groq\n```\n\n### Request and Response Data Flow Sequence\n\nThe system supports two primary request handling paradigms. The sequence diagram below shows both the standard conversational filing path (JWT-secured REST via Spring Boot) and the advanced deep legal research pipeline (direct client SSE connection to Python NLP-Orchestrator).\n\n```mermaid\nsequenceDiagram\n    autonumber\n    actor User as Citizen \u002F Litigant\n    participant FE as Frontend (React UI)\n    participant BE as Backend (Spring Boot)\n    participant BHA as Bhashini Translation API\n    participant GPT as LawGPT Service\n    participant NLP as NLP Orchestrator\n    participant DB as PostgreSQL\n    participant AI as AI Services (Groq \u002F Gemini \u002F Ollama)\n\n    %% Session A: Conversational Filing Flow\n    Note over User, AI: Pathway A: Conversational Case Filing (Standard REST Flow)\n    User->>FE: Submits query \u002F voice input in Indic language\n    FE->>BE: POST \u002Fapi\u002Fvakil-friend\u002Fchat\u002F{sessionId} (English or Indic)\n    activate BE\n    BE->>BHA: Speech-To-Text \u002F Translate input query to English\n    BHA-->>BE: Returns English translation\n    BE->>GPT: POST \u002Fcontext (English query RAG lookup)\n    activate GPT\n    GPT-->>BE: Returns top-3 FAISS semantic document chunks\n    deactivate GPT\n    BE->>AI: Chat completion request (System Prompt + Legal Context + English query)\n    activate AI\n    AI-->>BE: Returns structured legal response (English)\n    deactivate AI\n    BE->>BHA: Translate response back to original Indic language\n    BHA-->>BE: Returns translated response\n    BE->>DB: Log encrypted interaction to Case Diary (SHA-256 protected)\n    BE-->>FE: Return localized response & readyToFile heuristic flag\n    deactivate BE\n    FE-->>User: Renders text response & speaks via TTS \u002F lip-syncs Avatar\n\n    %% Session B: Deep Legal Research Flow\n    Note over User, AI: Pathway B: Deep Legal Research (SSE Streaming Flow)\n    User->>FE: Submits complex legal issue under Avatar page\n    FE->>NLP: EventSource: POST \u002Fresearch\u002Fdeep (Starts SSE Connection)\n    activate NLP\n    NLP->>AI: Stage 1: Detect domain & query complexity\n    AI-->>NLP: Domain classification details\n    NLP-->>FE: SSE: stage [understanding]\n    NLP->>AI: Stage 2: Decompile into sub-questions & route\n    AI-->>NLP: Sub-questions returned\n    NLP-->>FE: SSE: sub_questions\n    NLP->>AI: Stage 3: Query Indian Kanoon API for search criteria\n    AI-->>NLP: Search results \u002F Context returned\n    NLP-->>FE: SSE: kanoon_results (Top citations)\n    NLP->>AI: Stage 4: Run Parallel Research (Groq \u002F Gemini)\n    AI-->>NLP: Streaming sub-answers \u002F reasoning\n    NLP-->>FE: SSE: reasoning (Real-time token chunks)\n    NLP->>AI: Stage 5: Verdict & synthesis (Verify citations + Convert to Hinglish)\n    AI-->>NLP: Final Hinglish dialogue + validated markdown\n    NLP-->>FE: SSE: final (Markdown, Hinglish audio dialogue, citations)\n    NLP-->>FE: SSE: done\n    deactivate NLP\n    FE-->>User: Streams markdown verdict to screen & speaks Hinglish speech via Avatar\n```\n\n\u003Chr\u002F>\n\n## API Versioning Strategy\n\nThis project implements a robust API versioning strategy starting from `v1`. \n- The stable release of our APIs is accessible under the `\u002Fapi\u002Fv1\u002F` prefix.\n- A global `WebMvcConfigurer` automatically prefixes all backend controllers. \n- Any future breaking changes will be introduced under a new version (e.g., `\u002Fapi\u002Fv2\u002F`), ensuring backward compatibility for existing client applications.\n\n## Quick Start\n\nFor complete setup instructions, environment configuration, and Docker deployment details, refer to the **[Detailed Setup Guide](.\u002Fdocs\u002Fsetup.md)**.\n\nAt a high level, the platform consists of three services that need to run concurrently:\n\n| Service | Directory | Command |\n|---|---|---|\n| Frontend | `frontend\u002Fnyaysetu-frontend\u002F` | `npm install && npm run dev` |\n| Backend | `backend\u002Fnyaysetu-backend\u002F` | `mvn spring-boot:run` |\n| NLP Orchestrator | `nlp-orchestrator\u002F` | `uvicorn main:app --reload` |\n\n> **Prerequisites:** Node.js >= 20, Java 17, Maven 3.9+, PostgreSQL 15+, Python 3.12+\n\nFor environment variables, copy `.env.example` to `.env` and fill in your values. A full reference of all required variables is documented in the [Setup Guide](.\u002Fdocs\u002Fsetup.md#environment-variables).\n\n\u003Chr\u002F>\n\n## Documentation\n\n### Getting Started\n| Document | Description |\n|---|---|\n| [API Quick Start](.\u002FAPI_QUICKSTART.md) | 5-minute introduction to APIs (start here!) |\n| [Setup Guide](.\u002Fdocs\u002Fsetup.md) | Full database setup, environment variables, and Docker configuration |\n| [Architecture Overview](.\u002Fdocs\u002Farchitecture\u002Foverview.md) | System design, component diagrams, and data flow |\n\n### API Documentation & Integration\n| Document | Description |\n|---|---|\n| [OpenAPI\u002FSwagger Spec](.\u002Fopenapi.yaml) | Complete API specification in OpenAPI 3.0 format |\n| [API Testing Guide](.\u002FAPI_TESTING_GUIDE.md) | Comprehensive guide for testing APIs with Postman, cURL, Python, JavaScript |\n| [API Endpoints Reference](.\u002FAPI_ENDPOINTS_COMPREHENSIVE.md) | Detailed documentation of all 100+ endpoints with request\u002Fresponse schemas |\n| [API Quick Reference](.\u002FAPI_QUICK_REFERENCE.md) | Quick lookup table for endpoints by user role and service |\n| [API Integration Checklist](.\u002FAPI_INTEGRATION_CHECKLIST.md) | Step-by-step checklist for integrating APIs into applications |\n| [Postman Collection](.\u002FNyay_Setu_API_Collection.postman_collection.json) | Ready-to-import Postman collection with all endpoints and examples |\n\n### Additional Resources\n| Document | Description |\n|---|---|\n| [AI Integration Guide](.\u002FAI_INTEGRATION_GUIDE.md) | Groq API and NLP orchestrator technical deep-dive |\n| [API Documentation](.\u002FSYSTEM_DOCUMENTATION.md) | All REST endpoints with request and response specifications |\n| [Postman Collection](.\u002Fpostman_collection.json) | Postman collection (v2.1) for testing Spring Boot & Python APIs |\n| [OpenAPI Specification](.\u002Fdocs\u002Fopenapi.yaml) | OpenAPI 3.0 YAML spec for all endpoints |\n| [Contributing Guidelines](.\u002FCONTRIBUTING.md) | Branching strategy, commit conventions, and PR workflow |\n\n### API Testing\n\nTo easily test the backend APIs:\n1. **Import the Postman Collection**: Import the `postman_collection.json` file located in the project root into Postman.\n2. **Configure Environment Variables**:\n   - `baseUrl`: Set to `http:\u002F\u002Flocalhost:8080` (Spring Boot backend)\n   - `nlpUrl`: Set to `http:\u002F\u002Flocalhost:8001` (Python services)\n   - `bearerToken`: Set to the JWT token returned after registering\u002Flogging in.\n3. **Authentication**: All authenticated endpoints automatically inherit the Bearer Token from the collection properties. Simply register or login via the `Authentication` folder, copy the `token` (or `accessToken`), and save it in the `bearerToken` variable.\n4. **OpenAPI Spec**: You can also import `docs\u002Fopenapi.yaml` into Swagger Editor or your preferred OpenAPI client to visualize and interact with the endpoints.\n\n\u003Chr\u002F>\n\n## Contributing\n\nThis project is part of **GSSoC (GirlScript Summer of Code) 2026**. Contributions are welcome from everyone, regardless of experience level.\n\n**Before opening a Pull Request:**\n\n| Requirement | Details |\n|---|---|\n| Read the guidelines | Review [CONTRIBUTING.md](.\u002FCONTRIBUTING.md) for our branching and commit conventions |\n| Link an issue | Every PR must reference the issue it closes (`Closes #123`) |\n| Include visuals | UI-affecting PRs must include screenshots or a screen recording |\n| Sync with main | Rebase or merge `main` into your branch before requesting review |\n| Pass all checks | CI checks for lint, tests, and build must all pass |\n\nBrowse [open issues](https:\u002F\u002Fgithub.com\u002Fviru0909-dev\u002Fnyay-setu-working\u002Fissues) and filter by `good first issue` to get started.\n\n\u003Chr\u002F>\n\n## Troubleshooting\n\n### Common Setup Issues\n\n#### 1. npm install fails\n- Ensure Node.js version is `>= 20`\n- Delete `node_modules` and reinstall dependencies:\n\n```bash\nrm -rf node_modules\nnpm install\n```\n\n---\n\n#### 2. PostgreSQL connection issues\n- Verify PostgreSQL service is running\n- Check database credentials in `.env`\n- Ensure database and user are created properly\n\n---\n\n#### 3. Java version mismatch\nVerify Java version:\n\n```bash\njava -version\n```\n\nEnsure Java 17 is installed and configured correctly.\n\n---\n\n#### 4. Missing environment variables\n- Copy `.env.example` to `.env`\n- Fill all required variables before starting services\n\n---\n\n#### 5. Backend server not starting\n- Ensure PostgreSQL is running\n- Verify Maven installation:\n\n```bash\nmvn -version\n```\n\n- Check all dependencies are installed properly\n\n---\n\n#### 6. Port already in use\nStop conflicting processes or use different ports.\n\nExample:\n\n```bash\nnpx kill-port 3000\n```\n\n## Contributors\n\n\u003Cbr\u002F>\n\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fviru0909-dev\u002Fnyay-setu-working\u002Fgraphs\u002Fcontributors\">\n  \u003Cimg src=\"https:\u002F\u002Fcontrib.rocks\u002Fimage?repo=viru0909-dev\u002Fnyay-setu-working&max=500&columns=15\" alt=\"Contributors\" \u002F>\n\u003C\u002Fa>\n\n\u003Cbr\u002F>\u003Cbr\u002F>\n\nThis chart updates automatically as new contributors merge pull requests. Want to see your avatar here? [Pick up an issue](https:\u002F\u002Fgithub.com\u002Fviru0909-dev\u002Fnyay-setu-working\u002Fissues) and start contributing.\n\n\u003Chr\u002F>\n\n## License\n\nThis project is licensed under the **MIT License**. See the [LICENSE](.\u002FLICENSE) file for the full license text and guidelines on bulk-adding license headers to all source files in the repository.\n\n\u003Chr\u002F>\n\n\u003Cp align=\"center\">\n  Built with purpose for a more accessible Indian Judiciary.\u003Cbr\u002F>\n  \u003Cem>Nyay Setu — न्याय हर किसी का अधिकार है।\u003C\u002Fem>\n\u003C\u002Fp>\n## Local Development Setup\n\n### Prerequisites\n\n- Node.js\n- Java 17\n- Maven\n- Python 3.10+\n- Git\n\n---\n\n### Clone Repository\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Fviru0909-dev\u002Fnyay-setu-working.git\ncd nyay-setu-working\n```\n\n---\n\n### Frontend Setup\n\n```bash\ncd frontend\u002Fnyaysetu-frontend\nnpm install\nnpm run dev\n```\n\nFrontend runs on:\n\n```bash\nhttp:\u002F\u002Flocalhost:5173\n```\n\n---\n\n### Backend Setup\n\n```bash\ncd backend\u002Fnyaysetu-backend\nmvn spring-boot:run\n```\n\nBackend runs on:\n\n```bash\nhttp:\u002F\u002Flocalhost:8080\n```\n\n---\n\n### NLP Service Setup\n\n```bash\ncd nlp-orchestrator\npip install -r requirements.txt\npython main.py\n```\n\n---\n\n### Common Issues\n\n#### Login \u002F Network Error\n\nEnsure backend is running before starting frontend login flow.\n\n#### Maven Errors\n\nAlways run Maven commands inside:\n\n```bash\nbackend\u002Fnyaysetu-backend\n```\n\n#### Deployment Build Errors\n\nLinux deployment environments are case-sensitive.\nEnsure import paths exactly match filenames.","Nyay Setu 是一个旨在数字化印度司法系统的平台。该项目通过提供AI法律助手、基于角色的仪表板和端到端案件管理等核心功能，解决了高昂的法律成本、复杂的流程以及地理距离带来的障碍。技术上，它使用JavaScript构建，并且其AI助手Vakil Friend基于Groq的Llama 3.1模型开发，能够以易懂的语言帮助用户理解法律权利、处理案件文件及审查文档。此项目适用于需要简化法律程序访问途径的各种场景，包括但不限于公民个人、律师、法官以及其他司法体系内的工作人员。",2,"2026-06-11 04:10:41","trending"]