How sarveshsonkusre02/nv-protocol works
nvenv is a local-first credential vault and execution-time proxy: users store secrets, replace plaintext values with nv:// placeholders, then launch applications through an instrumented runner. The runner starts the TLS interception proxy; proxy requests are policy-checked, resolved from the encrypted vault, audited, and forwarded to external services. Separate CLI capabilities provide migration and vault management, Git credential lookup, and an MCP interface. Edges follow the supplied excerpts or explicit README statements; unsampled internals are not inferred.
Main entry points: proxy.py TLS proxy · mcp_server.py MCP server · runner.py Runtime runner · vault.py Encrypted vault
Components 15
User interfaces
- CLI entry
py_wrapper/cli.py - Vault commands
py_wrapper/nv.py - Git helper
py_wrapper/git.py - MCP server
py_wrapper/mcp_server.py
Execution runtime
- Application
- Runtime runner
py_wrapper/runner.py - TLS proxy
py_wrapper/proxy.py - Certificate authority
py_wrapper/ca.py
Secret controls
- Policy engine
py_wrapper/policy.py - Audit logger
py_wrapper/nv_audit.py - Encrypted vault
py_wrapper/vault.py
External integrations
- AI agent
- Git
- External API
Other components
- Developer
Connections 20
- Developer → CLI entry: runs commands
README.md - CLI entry → Vault commands: dispatches to
py_wrapper/cli.py - Vault commands → Encrypted vault: manages secrets
py_wrapper/nv.py - Vault commands → Runtime runner: starts runtime
py_wrapper/nv.py - Developer → Application: uses placeholders
README.md - Application → Runtime runner: launched through
README.md - Runtime runner → TLS proxy: starts proxy
py_wrapper/runner.py - Runtime runner → Certificate authority: creates CA
py_wrapper/runner.py - TLS proxy → Certificate authority: signs certificates
py_wrapper/proxy.py - TLS proxy → Policy engine: validates requests
py_wrapper/proxy.py - TLS proxy → Encrypted vault: retrieves secrets
py_wrapper/proxy.py - TLS proxy → Audit logger: logs requests
py_wrapper/proxy.py - TLS proxy → External API: forwards TLS
README.md - Developer → Git helper: configures helper
README.md - Git → Git helper: requests credentials
README.md - Git helper → Encrypted vault: looks up token
py_wrapper/git.py - Developer → MCP server: starts server
README.md - AI agent → MCP server: calls tools
README.md - MCP server → Encrypted vault: lists keys
py_wrapper/mcp_server.py - MCP server → Policy engine: checks policy
py_wrapper/mcp_server.py