DeepLaw 2.0 is a read-only Agent Knowledge Base for Chinese legal sources. The repository distributes code under Apache License 2.0; it does not distribute legal-source packages, case documents, generated release databases, or OCR corpora.

Security fixes are evaluated for the current software release, v0.3.0, and the main branch. Older versions, local knowledge-release artifacts, and third-party packages are not separately supported unless a release notice says otherwise.

Do not open a public issue, discussion, pull request, or social-media post with vulnerability details.

Use the repository Security page and select Report a vulnerability:

https://github.com/Eysn0130/DeepLaw/security/advisories/new

If that control is not available, do not disclose the details publicly. Open at most a detail-free issue asking the maintainer to enable a private reporting channel, then wait for a private channel before sharing technical information. Do not place an exploit, affected path, credential, private identifier, or sensitive log in that public request.

Include privately, when safe:

• the affected commit or version;
• impact and the boundary crossed;
• a minimal reproduction using synthetic or source-free data;
• whether credentials, case-private data, legal-source text, or release artifacts may have been exposed;
• a suggested mitigation, if known.

Never send live credentials, real case materials, private user identifiers, source DOCX/PDF files, generated SQLite releases, full OCR text, or unredacted host logs. Describe sensitive material and provide the smallest synthetic reproduction instead.

The project does not currently promise a response or remediation SLA. The maintainer will coordinate disclosure and remediation on a best-effort basis. Please keep the report private until a fix or an agreed disclosure date exists.

Examples of security-relevant reports include:

• a write path or command execution reachable through the read-only runtime;
• path traversal, symlink escape, or release-boundary bypass;
• receipt, hash, release pinning, or immutable-database verification bypass;
• official-catalog signature bypass, signing-key exposure, or trust-store confusion;
• leakage of credentials, case-private data, host paths, or provider-visible data beyond the documented budget;
• unsafe archive, parser, MCP, or dependency behavior with a concrete impact.

Legal interpretation disagreements, source-currentness corrections, retrieval quality suggestions, and documentation errors are normally not security vulnerabilities. They may be reported through a public issue only when the report contains no private, licensed, or otherwise restricted material.

The single-maintainer catalog-signing key is stored outside the repository at ~/.config/deeplaw/signing/official-catalog-ed25519.pem by default. Its parent directory is mode 0700 and the key is mode 0600; only public keys and detached signatures belong in Git. DEEPLAW_SIGNING_KEY_FILE may point to another dedicated owner-only location. Never attach the private key to an issue, pull request, CI secret dump, log, backup artifact, or release package.

If key exposure is suspected, stop signing, report it through the private channel, publish a package update whose trust store revokes the affected public key and adds a replacement, then sign the next monotonic catalog with the replacement. Existing clients still require the trusted package update; the catalog signature mechanism is not an online revocation or freeze-detection service.

This policy does not authorize access to systems, accounts, data, or legal sources that you do not own or have permission to test. Test only with synthetic data or material you are authorized to use.