๐Ÿ›ก๏ธ Nadhi Audit Official Documentation

Developer & Security Documentation

Minimal, practical guides for local installation, MCP integration, compliance frameworks, and automated AST code fixes.

โšก

Installation & Quick Start

Download and run Nadhi Audit locally on your Mac with Apple Silicon or Intel chips.

macOS 12+

1. Download and Install

Download the notarized macOS disk image (.dmg) and drag Nadhi Audit into your Applications folder.

Terminal / Snippet
# Available production builds for macOS 12+ โ€ข Apple Silicon (arm64): NadhiAudit-Mac-2.1.2-arm64.dmg โ€ข Intel Mac (x64): NadhiAudit-Mac-2.1.2-x64.dmg

2. Launch & License Activation

Open Nadhi Audit. On first launch, enter your license key. You can claim a free 1-year community key from the homepage or use your commercial license key.

Terminal / Snippet
Key Format: CVAI-XXXX-XXXX-XXXX-XXXX

3. Local Model Verification

Nadhi Audit bundles the fine-tuned local model (Nadhi_Audit_FT.gguf) and starts llama-server automatically on Apple Silicon Metal GPU. Zero configuration required.

๐Ÿค–

Cursor & Claude Code MCP Integration

Drive compliance audits, code fixes, and pull requests directly inside Cursor, Claude Code, VS Code, and Windsurf.

Model Context Protocol

1. Cursor IDE Setup (GUI or Config)

In Cursor, navigate to Cursor Settings โ†’ Features โ†’ MCP โ†’ Add New MCP Server, or create a configuration file in your project root at .cursor/mcp.json:

Terminal / Snippet
// .cursor/mcp.json (in project root or ~/.cursor/mcp.json) { "mcpServers": { "nadhi-audit": { "url": "http://127.0.0.1:8765/mcp" } } }

2. Claude Code CLI Setup

Run this command in your terminal to connect Claude Code to your local Nadhi Audit daemon:

Terminal / Snippet
claude mcp add --transport http nadhi-audit http://127.0.0.1:8765/mcp

3. VS Code (Cline / Roo Code) & Windsurf Setup

In VS Code MCP or Windsurf, add Nadhi Audit to your MCP server configuration:

Terminal / Snippet
// mcp_config.json { "mcpServers": { "nadhi-audit": { "url": "http://127.0.0.1:8765/mcp" } } }

4. Available Tools & Slash Prompts

Once connected, you can invoke these tools in Cursor Composer, Claude Code, and chat:

Command or ToolDescription
/auditRun compliance and security audit over the active repository.
/fixApply automated AST-verified fixes on an isolated git branch.
/push-prPush the remediation branch to GitHub and create a Pull Request.
/full_auditAll-in-one: Audits code, evaluates false positives, fixes bugs, and pushes PR.
audit_changesFast incremental audit checking only modified files.
audit_refAudit a remote Git commit without cloning source to disk (for CI).
get_last_reportRetrieve the last markdown report and PDF path instantly.

5. Example Prompts in Cursor & Claude Code

You can prompt your editor agent naturally with tool calling:

Terminal / Snippet
โ€ข "Audit this repository for OWASP Top 10 security vulnerabilities." โ€ข "Apply verified code fixes for all critical findings on a new branch." โ€ข "Run full_audit_fix_and_push to audit, repair, and create a Pull Request on GitHub."
๐Ÿ™

GitHub Authentication & CLI Setup

Configure GitHub CLI and Personal Access Tokens for private repository auditing and 1-click PR creation.

Remote VCS

1. GitHub CLI Setup (Recommended)

Install and authenticate the official GitHub CLI to allow Nadhi Audit to create forks and pull requests automatically:

Terminal / Snippet
# 1. Install GitHub CLI brew install gh # 2. Authenticate with GitHub gh auth login # 3. Verify authentication status gh auth status

2. Connecting Private Repositories via PAT

If you do not use GitHub CLI, generate a Read-Only Personal Access Token (repo scope) and authenticate via chat or Settings:

Terminal / Snippet
# In Nadhi Audit Chat or Terminal: run(command="vcs auth github ghp_yourPersonalAccessTokenHere")
๐Ÿ›ก๏ธ

Compliance Frameworks & Toggles

Switch between global software security standards and regional privacy compliance mandates in one click.

4 Regimes

1. Security (OWASP Top 10 / CWE) (Global Default)

Evaluates code for critical vulnerabilities: SQL injection (CWE-89), OS command injection (CWE-78), Cross-Site Scripting (CWE-79), Path traversal (CWE-22), Broken access control, Disabled TLS verification (CWE-295), and Hardcoded credentials (CWE-798).

2. India DPDP Act 2023 & Rules 2025

Audits data fiduciary obligations: Section 8(5) reasonable security safeguards, Rule 6 security log retention (minimum 1 year), personal data in logs (CWE-532), and data principal rights.

3. US HIPAA Health Compliance

Audits protected health information (PHI) safeguards: ยง164.312 transmission encryption, access control, audit logging, and cleartext medical identifiers.

4. European Union GDPR

Audits Article 32 security of processing, Article 30 records, and Chapter V cross-border transfer controls.

How to Switch Frameworks

Select your active framework in Nadhi Audit Settings, or pass the framework name directly when running an audit:

Terminal / Snippet
# In Chat or MCP: /audit /path/to/project security /audit /path/to/project dpdp /audit /path/to/project hipaa /audit /path/to/project gdpr
๐Ÿ› ๏ธ

Automated AST-Verified Code Fixing

How Nadhi Audit fixes vulnerabilities safely on an isolated branch with compiler and judge verification.

Multi-Strategy Repair

Multi-Strategy Remediation Loop

When you run /fix or full_audit_fix_and_push, Nadhi Audit executes a LangGraph state machine with 3 progressive repair strategies:

  • โœ“Pre-Fix False Positive Filter: Local model evaluates finding context. Skips test fixtures, mocks, and protocol requirements.
  • โœ“Strategy 1 (Direct Find/Replace): Precise line replacement with line-prefix normalization.
  • โœ“Strategy 2 (Contextual Block Repair): Expands context window and injects compiler feedback to prevent repeating syntax mistakes.
  • โœ“Strategy 3 (AST / ReAct Graph): Scoped function-level AST transformation.

Compiler & AST Syntax Gate

Before any code edit is kept, Nadhi Audit re-parses and tests the patched file using language interpreters in check-only mode:

Terminal / Snippet
โ€ข JavaScript / TypeScript: node --check โ€ข Python: python3 -m py_compile โ€ข PHP: php -l โ€ข Ruby: ruby -c โ€ข JSON: JSON.parse validation

LLM-as-a-Judge Review

The local model compares the original and patched diff. It validates that the vulnerability is removed, program semantics are preserved, and no undefined variables were introduced. Clean edits are committed to the isolated nadhi branch with DCO sign-offs.

๐Ÿ“„

Executive Audit Reports (PDF)

Generate formal compliance reports with findings, evidence lines, and methodology.

Auditor-Ready

Report Structure

Every audit generates a markdown summary in the workspace and an executive PDF document containing:

  • โœ“Report ID and timestamp for audit reproducibility.
  • โœ“Target repository path and exact files scanned.
  • โœ“Severity breakdown: Critical, High, Medium, Low.
  • โœ“Citable clause mappings (e.g. OWASP A01:2021, DPDP Sec 8(5), HIPAA ยง164.312).
  • โœ“Evidence quotes citing exact file and line numbers.
  • โœ“Assessor review and approval sign-off block.

Report File Location

Reports are stored in your selected workspace folder under: ~/Desktop/Nadhi-Audit/<repo-name>/security-audit-report-*.pdf

๐ŸŒ

Self-Hosted Ollama Support

Route inference to a central GPU workstation or private server on your local network.

LAN Server

Connecting to a LAN Ollama Server

To use a central server instead of your Mac local model, open Settings in Nadhi Audit and configure:

Terminal / Snippet
1. Enable "Self-Hosted Ollama Server" 2. Ollama Server URL: http://192.168.1.100:11434 3. Model Name: llama3.3:70b or gemma2:27b

Airgapped Integrity

In Ollama mode, network egress remains strictly blocked from public internet. Traffic only flows over private RFC1918 loopback and local network addresses.