open-agreements-353a14 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited open-agreements-353a14 (Plugin) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
<!-- This file is generated from README.template.md by scripts/generate_readme.mjs. Do not edit README.md directly. -->
<p align="center"> <img src="https://raw.githubusercontent.com/open-agreements/open-agreements/main/docs/assets/oa-seal.svg" alt="OpenAgreements seal" width="140"> </p>
OpenAgreements helps people and software agents find primary-source-backed U.S. legal guidance and produce reviewable DOCX files from standard agreement templates.
machine-readable formats.
OpenAgreements provides legal information and document mechanics, not legal advice. It does not decide whether a form or clause is right for a transaction, and generated documents are drafts for human review.
The project’s longer-term goal is a citable conformance layer for legal AI: primary law becomes inspectable requirements, an AI can check a document against them, and a lawyer owns the final call. Read Why OpenAgreements Exists for the rationale; this README stays focused on using the project.
Install the CLI locally, inspect the available forms, and fill the Common Paper Mutual NDA:
npm install -g open-agreements
open-agreements list
open-agreements fill common-paper-mutual-nda \
--set party_1_name="Jane Doe" \
--set party_1_company="Acme Manufacturing, Inc." \
--set party_2_name="John Smith" \
--set party_2_company="Northeast Logistics LLC" \
--set effective_date="2026-07-15" \
--set purpose="Evaluating a potential logistics relationship" \
--output mutual-nda.docxThe last command writes mutual-nda.docx. Open it in Word or another DOCX viewer and review every filled term before signature. Defaults supply the standard one-year term, Delaware governing law, and other omitted cover terms; the CLI reports any priority fields that still need attention.
For a complete, copyable example and field-review steps, follow the quick start.
standard form + source and license metadata
→ supplied field values
→ validation and local rendering
→ reviewable DOCX
→ human legal and business reviewThe standard form is authoritative until rendering. Your supplied values become the transaction-specific inputs. The generated DOCX is an output for review; it is never automatically accepted or signed.
The legal-content path is separate: practice guides cite primary sources, surveys compare jurisdictions, and checklists turn requirements into review steps. Those materials can inform a decision, but they do not mutate an agreement.
Links: Website | Template Catalog | Docs | Trust | npm
after the response is returned.
Choose an execution mode that matches your document-sensitivity and internal policy requirements. See the trust-boundary status and security policy.
Project code is licensed under Apache License 2.0. Content retains its source-specific license. See the licensing reference and each template's metadata.yaml before redistribution or modification.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.