Skip to content
contract.cli

Install

Three installs, one workflow.

Each CLI is a standalone package on its native registry. Install whichever ones you need; they don't depend on each other and there's no shared runtime to set up.

TL;DR — pipx install nda-review-cli · npm i -g docx2pdf-cli · npm i -g sign-cli. Verify with --version on each.

Prerequisites

  • Python 3.9+ with pipx for nda-review-cli. Install pipx via brew install pipx or your distro package manager, then pipx ensurepath.
  • Node.js 18+ for sign-cli and docx2pdf-cli. Install via brew install node, nvm, or your platform's installer.
  • A PDF backend (only for docx2pdf-cli) — LibreOffice, Microsoft Word, Pandoc, or a Gotenberg server. The tool auto-detects what's installed.

nda-review-cli

The Python CLI for drafting, reviewing, and negotiating NDAs. Stdlib-only at runtime — pipx installs it cleanly into its own environment.

pipx install nda-review-cli
nda-review-cli --version

Recommended — isolates dependencies and adds the CLI to your $PATH.

first-run setup
# 16 quick questions write your house policy
nda-review-cli quickstart

docx2pdf-cli

The Node.js CLI for DOCX → PDF conversion with hybrid backends.

npm i -g docx2pdf-cli
docx2pdf --version
sanity check
# Probe what backends are detected on this machine
docx2pdf --doctor
docx2pdf --list-backends

The --doctor probe walks every backend candidate (LibreOffice, Word, Pandoc, Gotenberg) and reports which ones are usable. Pick one with --backend or let the tool auto-select.

sign-cli

The TypeScript CLI for fully-offline PAdES signing (built-in PKCS#7 signer with a self-issued cert) plus optional Dropbox Sign / DocuSign / SignWell routing. Installs as sign on your PATH.

npm i -g sign-cli
sign --version

The offline demo walks the full lifecycle (create → approve → send → sign → audit verify → bundle export) using the built-in local PAdES signer — no signup, no third-party calls, ~5 seconds end to end. After install, run sign init for a guided provider setup or sign doctor preflight for a structured per-check readiness report.

Configuration locations

Each tool keeps its config in standard places. Nothing is shared across tools.

Tool Config Sensitive bits
nda-review-cli config/org-policy.json, profiles/, optional config/llm.json LLM provider keys (gitignored)
docx2pdf-cli Optional .docx2pdfrc Gotenberg URL if remote backend in use
sign-cli $XDG_CONFIG_HOME/sign-cli/profiles.json (named profile bundles) · project-level sign-profile.json (git-style upward discovery) · env vars (SIGN_PROFILE, SIGN_DB_PATH, etc.) Provider API keys via shell env + {{env:VAR}} profile references — credentials never live in the profile file

Updating

pipx upgrade nda-review-cli
npm update -g docx2pdf-cli sign-cli

Uninstalling

Each tool comes off cleanly. There are no daemons, services, or system-wide modifications to clean up afterwards.

pipx uninstall nda-review-cli
npm rm -g docx2pdf-cli sign-cli

Edit this page on GitHub