dvalincode 0.14.0 → 0.15.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (75) hide show
  1. package/README.md +159 -60
  2. package/README.zh-CN.md +169 -72
  3. package/THIRD_PARTY_NOTICES.md +295 -147
  4. package/dist/agent/loop.d.ts +8 -0
  5. package/dist/agent/loop.js +8 -1
  6. package/dist/agent/loop.js.map +1 -1
  7. package/dist/agent/runner.d.ts +1 -0
  8. package/dist/agent/runner.js +10 -1
  9. package/dist/agent/runner.js.map +1 -1
  10. package/dist/agent/session.d.ts +23 -1
  11. package/dist/agent/session.js +63 -11
  12. package/dist/agent/session.js.map +1 -1
  13. package/dist/agent/types.d.ts +2 -0
  14. package/dist/audit/log.d.ts +3 -0
  15. package/dist/audit/log.js.map +1 -1
  16. package/dist/audit/report.js +2 -0
  17. package/dist/audit/report.js.map +1 -1
  18. package/dist/cli.js +24 -2
  19. package/dist/cli.js.map +1 -1
  20. package/dist/commands/dvalin.js +12 -0
  21. package/dist/commands/dvalin.js.map +1 -1
  22. package/dist/commands/mcpServe.d.ts +2 -0
  23. package/dist/commands/mcpServe.js +36 -0
  24. package/dist/commands/mcpServe.js.map +1 -0
  25. package/dist/commands/policy.js +12 -0
  26. package/dist/commands/policy.js.map +1 -1
  27. package/dist/commands/run.d.ts +30 -0
  28. package/dist/commands/run.js +229 -0
  29. package/dist/commands/run.js.map +1 -0
  30. package/dist/core/policy.d.ts +21 -0
  31. package/dist/core/policy.js +32 -0
  32. package/dist/core/policy.js.map +1 -1
  33. package/dist/core/subprocessSandbox.d.ts +49 -6
  34. package/dist/core/subprocessSandbox.js +175 -64
  35. package/dist/core/subprocessSandbox.js.map +1 -1
  36. package/dist/core/trust.js +12 -0
  37. package/dist/core/trust.js.map +1 -1
  38. package/dist/harness/run.d.ts +70 -0
  39. package/dist/harness/run.js +185 -0
  40. package/dist/harness/run.js.map +1 -0
  41. package/dist/mcp/client.d.ts +12 -0
  42. package/dist/mcp/client.js +2 -2
  43. package/dist/mcp/client.js.map +1 -1
  44. package/dist/mcp/config.d.ts +33 -3
  45. package/dist/mcp/config.js +32 -3
  46. package/dist/mcp/config.js.map +1 -1
  47. package/dist/mcp/register.d.ts +23 -6
  48. package/dist/mcp/register.js +42 -8
  49. package/dist/mcp/register.js.map +1 -1
  50. package/dist/mcp/server.d.ts +35 -0
  51. package/dist/mcp/server.js +230 -0
  52. package/dist/mcp/server.js.map +1 -0
  53. package/dist/mcp/stdio.d.ts +34 -0
  54. package/dist/mcp/stdio.js +183 -0
  55. package/dist/mcp/stdio.js.map +1 -0
  56. package/dist/remediation/sarifExport.d.ts +7 -0
  57. package/dist/remediation/sarifExport.js +102 -0
  58. package/dist/remediation/sarifExport.js.map +1 -0
  59. package/dist/remediation/scannerSuite.js +11 -1
  60. package/dist/remediation/scannerSuite.js.map +1 -1
  61. package/dist/server/configStore.d.ts +2 -8
  62. package/dist/server/configStore.js +12 -7
  63. package/dist/server/configStore.js.map +1 -1
  64. package/dist/server/wsHandler.js +8 -0
  65. package/dist/server/wsHandler.js.map +1 -1
  66. package/dist/tools/shell.js +1 -1
  67. package/dist/tools/shell.js.map +1 -1
  68. package/dist/tui/app.js +4 -1
  69. package/dist/tui/app.js.map +1 -1
  70. package/dist/tui/render.d.ts +1 -0
  71. package/dist/tui/render.js +11 -0
  72. package/dist/tui/render.js.map +1 -1
  73. package/dist/version.d.ts +1 -1
  74. package/dist/version.js +1 -1
  75. package/package.json +4 -3
package/README.md CHANGED
@@ -9,48 +9,103 @@
9
9
  <p align="center">
10
10
  <a href="https://github.com/arthurpanhku/dvalincode/releases/latest"><img src="https://img.shields.io/github/v/release/arthurpanhku/dvalincode?style=for-the-badge&color=818cf8&label=Release" alt="Release"></a>
11
11
  <a href="https://github.com/arthurpanhku/dvalincode/releases"><img src="https://img.shields.io/github/downloads/arthurpanhku/dvalincode/total?style=for-the-badge&color=blue&label=Downloads" alt="Downloads"></a>
12
- <a href="#-tests"><img src="https://img.shields.io/badge/Tests-229%20%2F%20229%20%E2%9C%93-success?style=for-the-badge" alt="Tests"></a>
12
+ <a href="#-tests"><img src="https://img.shields.io/badge/Tests-323%20%2F%20323%20%E2%9C%93-success?style=for-the-badge" alt="Tests"></a>
13
13
  <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-green?style=for-the-badge" alt="License"></a>
14
14
  <a href="https://scorecard.dev/viewer/?uri=github.com/arthurpanhku/dvalincode"><img src="https://api.scorecard.dev/projects/github.com/arthurpanhku/dvalincode/badge" alt="OpenSSF Scorecard"></a>
15
- <a href="docs/governance/ISO-42001-AIMS.md"><img src="https://img.shields.io/badge/ISO%2FIEC%2042001-AIMS%20Aligned-0F766E?style=for-the-badge" alt="ISO/IEC 42001 AIMS aligned"></a>
16
- <a href="docs/EVIDENCE-PACK.md"><img src="https://img.shields.io/badge/Compliance-Evidence%20Pack-2563EB?style=for-the-badge" alt="Compliance evidence pack"></a>
17
- <a href="docs/security/OPENSSF-SCORECARD.md"><img src="https://img.shields.io/badge/DevSecOps-Native-B91C1C?style=for-the-badge" alt="DevSecOps native"></a>
18
15
  <a href="#-quick-install"><img src="https://img.shields.io/badge/Platforms-macOS%20·%20Windows%20·%20Linux-blue?style=for-the-badge" alt="Platforms"></a>
19
16
  <a href="#-providers"><img src="https://img.shields.io/badge/LLM-OpenAI%20·%20Claude%20·%20DeepSeek%20·%20Ollama%20·%20Groq-7C3AED?style=for-the-badge" alt="LLM Support"></a>
20
17
  <a href="README.zh-CN.md"><img src="https://img.shields.io/badge/i18n-EN%20·%20中文-orange?style=for-the-badge" alt="English / 中文"></a>
21
18
  </p>
22
19
 
23
20
  <p align="center">
24
- <b>The approvable coding agent for regulated teams.</b><br>
25
- <b>Built for finance, healthcare, and security-sensitive engineering where AI coding must be controllable, transparent, and auditable.</b>
21
+ <b>Find the security holes in your repo, fix them, and prove the fix — in one command.</b><br>
22
+ Every fix is diffed, tested, re-scanned, and recorded in a tamper-evident audit log before it can become a PR.
26
23
  </p>
27
24
 
28
- <p align="center">
29
- <b>🔑 Any model · local-first · policy-bound · audit-ready — the agent your security team can actually approve.</b>
30
- </p>
25
+ ---
31
26
 
32
- <p align="center">
33
- Bring your own model — DeepSeek, OpenAI, Claude (via OpenRouter), Groq, Ollama, or any OpenAI-compatible endpoint. Switch with one click, no code changes, no lock-in.
34
- </p>
27
+ ## ⏱️ 30 seconds, no install, no API key
35
28
 
36
- ---
29
+ ```sh
30
+ npx dvalincode dvalin .
31
+ ```
32
+
33
+ That is the whole thing. It runs the built-in rules for injection, hardcoded
34
+ secrets, XSS, `eval`, and unsafe shell use against the current directory and
35
+ prints what it found. No account, no model, no config, no code leaves your
36
+ machine. Add `--scanners builtin,semgrep,trivy,osv-scanner` to pull in whichever
37
+ of those engines you already have on `PATH`.
38
+
39
+ ### Or put it on every pull request — nothing to install at all
40
+
41
+ ```yaml
42
+ # .github/workflows/security.yml
43
+ permissions:
44
+ contents: read
45
+ security-events: write
46
+ steps:
47
+ - uses: actions/checkout@v5
48
+ - uses: arthurpanhku/dvalincode@v0.15.0
49
+ with:
50
+ fail-on: high
51
+ ```
37
52
 
38
- ## ⏱️ 60 seconds to proof
53
+ Findings land inline on the pull request diff and in your Security tab.
54
+ No API key, no secrets, no model — the scan is deterministic and local to the
55
+ runner. [Full example →](docs/examples/dvalin-scan.yml)
39
56
 
40
- Don't take the claims on trust — verify them on your own machine:
57
+ ### Then let it fix what it found
41
58
 
42
59
  ```sh
43
- curl -fsSL https://raw.githubusercontent.com/arthurpanhku/dvalincode/main/scripts/install.sh | bash
44
- dvalincode trust
60
+ dvalincode dvalin . --fix --verify --draft-pr
45
61
  ```
46
62
 
47
- `trust` prints this install's **live security posture**: the resolved org policy and its hash, per-boundary network enforcement (provider · shell · MCP), and the tamper-evident audit status — the exact evidence a security reviewer needs, straight from the tool itself.
63
+ This step *does* use a model — your model, any OpenAI-compatible endpoint. It
64
+ prepares focused repairs in an isolated worktree, runs your tests, and requires
65
+ a clean re-scan before anything can proceed to a draft PR. It never auto-merges,
66
+ and a clean scan is never treated as proof that the code is safe.
48
67
 
49
68
  <p align="center">
50
- <img src="assets/cli-trust.gif" alt="dvalincode trust — live security posture under an org policy" width="100%">
69
+ <img src="assets/dvalin-remediation.gif" alt="Dvalin scanning a vulnerable OWASP NodeGoat example at 22/100 F with 10 findings, then showing a clean verified re-scan at 100/100 A" width="100%">
51
70
  </p>
52
71
 
53
- Then let the agent work, and prove what it did after the fact:
72
+ This animation is made from the real application, not a mock. The input is an
73
+ Apache-2.0-licensed example adapted from
74
+ [OWASP NodeGoat](https://github.com/OWASP/NodeGoat/tree/c5cb68a7084e4ae7dcc60e6a98768720a81841e8/app/routes),
75
+ whose contribution route evaluated user-controlled text.
76
+
77
+ ## 🛡️ What that run actually did
78
+
79
+ Dvalin turns open-source scanner evidence into a controlled scan → fix → test →
80
+ re-scan → draft-PR workflow. Here is the run in the animation above, measured:
81
+
82
+ | Real NodeGoat-derived run | Before | After Dvalin remediation |
83
+ |---|---:|---:|
84
+ | Security health (triage heuristic) | 22 / 100 · F | 100 / 100 · A |
85
+ | Findings | 10 (`eval` across 3 rules, 2 engines) | 0 |
86
+ | Tests | 2 passing | 3 passing, including an injection regression test |
87
+ | Scanner fleet | 4 / 4 completed | 4 / 4 completed |
88
+
89
+ The scanning and hardening **control plane** uses open-source components:
90
+
91
+ - [Semgrep CE](https://github.com/semgrep/semgrep) and its community rules for
92
+ semantic SAST.
93
+ - [Trivy](https://github.com/aquasecurity/trivy) for filesystem vulnerabilities,
94
+ secrets, and misconfiguration.
95
+ - [OSV-Scanner](https://github.com/google/osv-scanner) with the open
96
+ [OSV database](https://osv.dev/) for dependency vulnerabilities.
97
+ - DvalinCode's MIT-licensed built-in rules, remediation orchestration, test and
98
+ re-scan gates, plus [SARIF 2.1](https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html)
99
+ import for other compatible scanners.
100
+
101
+ The scanners find and rank evidence. The configured model proposes source
102
+ changes; DvalinCode constrains that work, records the diff, runs project tests,
103
+ re-scans the changed tree, and keeps PR publication explicit. It does not
104
+ auto-merge and it does not claim that a clean scan proves the absence of bugs.
105
+ Choose an open-weight model through Ollama if the repair-proposal step must also
106
+ stay fully local and open; hosted model licensing depends on the provider.
107
+
108
+ You can still prove what the agent did after the fact:
54
109
 
55
110
  ```sh
56
111
  dvalincode report verify # re-derive the hash chain of the last run's audit log
@@ -58,6 +113,22 @@ dvalincode report verify # re-derive the hash chain of the last run's audit l
58
113
 
59
114
  ---
60
115
 
116
+ ## 🏛️ And it survives a security review
117
+
118
+ That last command is the part that matters once more than one person depends on
119
+ this. DvalinCode is a full coding agent — terminal, web GUI, and desktop app —
120
+ built so that an organization, not the developer, bounds what it may do: a
121
+ policy file constrains modes, commands, paths, tools, and models; every run is
122
+ hash-chained into a tamper-evident audit log; nothing reaches a provider that
123
+ the egress guard did not allow. A repo policy can only ever *narrow* the
124
+ machine-level one.
125
+
126
+ If you are the person who has to approve this class of tool, start at
127
+ [APPROVABILITY-PLAN.md](docs/APPROVABILITY-PLAN.md) and the
128
+ [Evidence Pack](docs/EVIDENCE-PACK.md) that every release ships of itself.
129
+
130
+ ---
131
+
61
132
  <table>
62
133
  <tr><td><b>🏠 Home</b></td><td>One place for read-only <b>Ask</b> and approval-gated <b>Collaborate</b> workflows. Switch intent without leaving the project or conversation.</td></tr>
63
134
  <tr><td><b>⚡ Code</b></td><td>Focused autonomous coding with full tool access and Ask / Plan / Auto / Bypass permission levels. Security and browser routines no longer compete with the core coding workflow.</td></tr>
@@ -67,7 +138,8 @@ dvalincode report verify # re-derive the hash chain of the last run's audit l
67
138
  <tr><td><b>📚 Skills</b></td><td>Upload, download, and inspect local skill bundles. DvalinCode ships built-in secure-code-scan and secure-code-remediation skills, plus agent tools for listing skills, reading skill instructions, scanning, listing cases, and preparing remediation worktrees. <a href="docs/SKILLS.md">Format →</a></td></tr>
68
139
  <tr><td><b>🛡️ Audit trail</b></td><td>Every run emits a tamper-evident, hash-chained JSONL log — every file read/written, every command, every approval. A Run Report renders it as Markdown; <code>dvalincode report verify</code> proves the chain is intact. <a href="docs/AUDIT-TRAIL.md">Threat model →</a></td></tr>
69
140
  <tr><td><b>🔒 Org policy &amp; <code>trust</code></b></td><td>A company — not the developer — bounds the agent. A <code>dvalin.policy.json</code> constrains modes, shell commands, file paths, tools, and models; a repo policy can only ever <i>narrow</i> the machine-level one, never widen it. Each run records the governing policy's hash. <code>dvalincode trust</code> prints the install's live security posture — active policy + hashes, audit status, runtime — so a reviewer can verify it directly. <a href="docs/POLICY-REFERENCE.md">Policy reference →</a> · <a href="docs/APPROVABILITY-PLAN.md">Approvability plan →</a></td></tr>
70
- <tr><td><b>🏛️ Governance evidence</b></td><td>OpenSSF Scorecard, CodeQL, Dependabot, pinned GitHub Actions, CODEOWNERS, and ISO/IEC 42001 AIMS alignment docs are maintained as reviewable project evidence. <a href="docs/security/OPENSSF-SCORECARD.md">Scorecard map →</a> · <a href="docs/governance/ISO-42001-AIMS.md">ISO 42001 alignment →</a></td></tr>
141
+ <tr><td><b>🏛️ Governance evidence</b></td><td>OpenSSF Scorecard, CodeQL, Dependabot, pinned GitHub Actions, CODEOWNERS, and ISO/IEC 42001 AIMS alignment docs are maintained as reviewable project evidence, and every release ships an Evidence Pack the binary produced of itself. <a href="docs/security/OPENSSF-SCORECARD.md">Scorecard map →</a> · <a href="docs/governance/ISO-42001-AIMS.md">ISO 42001 alignment →</a> · <a href="docs/RELEASE-EVIDENCE.md">Release evidence →</a></td></tr>
142
+ <tr><td><b>📐 Open specs</b></td><td><b>PCP-1</b> — the provider-boundary contract (egress containment, credential containment, audit, policy binding) written as a vendor-neutral profile with test procedures, so any agent runtime can run it against its own adapters and publish the result. Not a DvalinCode test file; a checklist anyone can hold us to as well. <a href="docs/spec/PROVIDER-CONFORMANCE.md">Provider Conformance Profile →</a></td></tr>
71
143
  <tr><td><b>🖥️ First-class GUI</b></td><td>Modern web UI with code highlighting, file <code>@</code>-references, <code>/</code> slash commands, Git branch indicator, live token + cost counter, multi-profile LLM config, and a dark / light / system theme switcher.</td></tr>
72
144
  <tr><td><b>🖥️ Terminal or web — one binary</b></td><td>Run it bare for an interactive <b>terminal agent</b> with streaming output, inline approvals, and red/green diffs, or <code>dvalincode serve</code> to host the <b>web GUI</b> for browser/remote use. Both frontends drive the same agent core.</td></tr>
73
145
  <tr><td><b>🖥️ Native desktop app</b></td><td><code>DvalinCode.app</code> — a real dock application (OS-native webview, no Electron) over the same engine. On macOS the one-line installer puts it in <code>/Applications</code> automatically; launch it straight from Launchpad.</td></tr>
@@ -126,6 +198,12 @@ it can touch production repositories.
126
198
 
127
199
  ## 🛡️ Security & Governance
128
200
 
201
+ <p align="center">
202
+ <a href="docs/governance/ISO-42001-AIMS.md"><img src="https://img.shields.io/badge/ISO%2FIEC%2042001-AIMS%20Aligned-0F766E?style=for-the-badge" alt="ISO/IEC 42001 AIMS aligned"></a>
203
+ <a href="docs/EVIDENCE-PACK.md"><img src="https://img.shields.io/badge/Compliance-Evidence%20Pack-2563EB?style=for-the-badge" alt="Compliance evidence pack"></a>
204
+ <a href="docs/security/OPENSSF-SCORECARD.md"><img src="https://img.shields.io/badge/DevSecOps-Native-B91C1C?style=for-the-badge" alt="DevSecOps native"></a>
205
+ </p>
206
+
129
207
  DvalinCode maintains project-level governance evidence for open-source and
130
208
  enterprise review. This is the differentiator for teams where AI coding must
131
209
  pass security approval before it can reach production repositories:
@@ -157,7 +235,7 @@ not claim third-party ISO certification.
157
235
 
158
236
  ---
159
237
 
160
- ## ⭐ What's New in v0.13.0 — Dvalin security engineering
238
+ ## ⭐ What's New in v0.14.0 — Dvalin security engineering
161
239
 
162
240
  - **Home unifies Chat and Cowork** — the GUI now has a single Home workspace
163
241
  with read-only Ask and approval-gated Collaborate intents, while keeping the
@@ -321,53 +399,32 @@ not claim third-party ISO certification.
321
399
 
322
400
  ## 📸 Preview
323
401
 
324
- <p align="center">
325
- <img src="assets/hero.png" alt="DvalinCode UI" width="100%">
326
- </p>
327
-
328
- **Switching modes — each mode has its own sidebar:**
329
-
330
- <p align="center">
331
- <img src="assets/modes.gif" alt="Mode switching" width="100%">
332
- </p>
333
-
334
- **Slash commands & file references in the composer:**
335
-
336
- <p align="center">
337
- <img src="assets/slash.gif" alt="Slash commands and @ file references" width="100%">
338
- </p>
339
-
340
- ### 🔒 Governance, from the command line
341
-
342
- **`dvalincode trust` — the install's live security posture (resolved policy, per-boundary enforcement, audit status) that a security review can read directly.** Field semantics and copy-paste recipes: [docs/POLICY-REFERENCE.md](docs/POLICY-REFERENCE.md).
402
+ **A real Dvalin scan of vulnerable code — Security health 22/100 · F, with the
403
+ 10 findings the engines actually reported, located to the line:**
343
404
 
344
405
  <p align="center">
345
- <img src="assets/cli-trust.gif" alt="dvalincode trust — live security posture under an org policy" width="100%">
406
+ <img src="assets/hero.png" alt="Dvalin Security health showing 22/100 F with 4 high and 6 medium findings, and a Findings list locating each eval to a line in the NodeGoat-derived route" width="100%">
346
407
  </p>
347
408
 
348
- **`dvalincode policy check` — validate `dvalin.policy.json` in CI: schema check, the resolved policy after machine-layer narrowing, and its canonical hash.**
409
+ **The verified result — the three `eval` call sites replaced by a constrained
410
+ numeric parser, one new injection regression test, all four open-source engines
411
+ complete, 0 findings, 100/100 · A:**
349
412
 
350
413
  <p align="center">
351
- <img src="assets/cli-policy.gif" alt="dvalincode policy check — validate and inspect the resolved org policy" width="100%">
414
+ <img src="assets/dvalin-scan-after.jpg" alt="Dvalin verified re-scan showing 100/100 A, zero findings, and the remediation run that produced it" width="100%">
352
415
  </p>
353
416
 
354
- **Tamper-evident audit — every agent run is a hash-chained, minimized report you can verify offline:**
417
+ **Home → Code → Dvalin — the current workspaces:**
355
418
 
356
419
  <p align="center">
357
- <img src="assets/cli-audit.gif" alt="dvalincode report — run report, then report verify proving the chain intact" width="100%">
420
+ <img src="assets/modes.gif" alt="DvalinCode switching between Home, Code, and Dvalin" width="100%">
358
421
  </p>
359
422
 
360
- **Evidence Pack — one command bundles policy, posture, and audit proofs into a single file a reviewer can verify fully offline:**
361
-
362
- <p align="center">
363
- <img src="assets/cli-evidence.gif" alt="dvalincode evidence export and verify — offline-verifiable governance evidence" width="100%">
364
- </p>
365
-
366
- **Project intelligence — `dvalincode scan` maps the workspace before the agent touches it:**
367
-
368
- <p align="center">
369
- <img src="assets/cli-scan.gif" alt="dvalincode scan — project intelligence" width="100%">
370
- </p>
423
+ The scan images above are unedited captures of a real run against the documented
424
+ NodeGoat-derived case: the scanners were run, the model repaired the source, the
425
+ project's tests were run, and the tree was re-scanned. Nothing is staged, and a
426
+ 100/A means the configured engines found nothing — not that the code is proven
427
+ safe.
371
428
 
372
429
  ---
373
430
 
@@ -401,8 +458,14 @@ dvalincode # interactive terminal agent
401
458
  dvalincode dvalin . # white-box security scan (GUI-independent)
402
459
  dvalincode serve # start the web GUI, open the browser
403
460
  dvalincode serve --host 0.0.0.0 --no-open # host it on a server for remote/browser use
461
+ echo "inspect src and summarize" | dvalincode run - --output-format stream-json
462
+ dvalincode mcp-serve # task-level stdio MCP server for external agents
404
463
  ```
405
464
 
465
+ Headless `run` and `mcp-serve` keep the same policy and audit chokepoint as
466
+ the interactive clients. See the [unattended recipes](docs/RECIPES-UNATTENDED.md)
467
+ for cron, CI, and external-agent examples.
468
+
406
469
  ### Windows
407
470
 
408
471
  Download `dvalincode-v*-windows-x64.zip` from [Releases](https://github.com/arthurpanhku/dvalincode/releases/latest), unzip, then double-click `start.bat`.
@@ -421,6 +484,18 @@ Grab the archive for your platform from the [Releases page](https://github.com/a
421
484
 
422
485
  Verify against `SHA256SUMS.txt` (included in each release).
423
486
 
487
+ Each release also ships **`dvalincode-v*-evidence.json`** — an Evidence Pack the
488
+ shipped binary produced of itself on the build machine: two real governed runs,
489
+ one allowed and one blocked by policy, with their hash chains. You can check the
490
+ claims on this page before installing anything:
491
+
492
+ ```sh
493
+ dvalincode evidence verify dvalincode-v0.14.0-evidence.json # offline, reads only the file
494
+ ```
495
+
496
+ The pack's checksum is inside `SHA256SUMS.txt`, which is the subject of the
497
+ release's build-provenance attestation. [How it is produced →](docs/RELEASE-EVIDENCE.md)
498
+
424
499
  > **macOS Gatekeeper:** binaries are unsigned. On first run, either clear the quarantine flag with `xattr -dr com.apple.quarantine ~/.dvalincode`, or right-click the binary in Finder → Open → confirm.
425
500
 
426
501
  ### Staying up to date
@@ -566,7 +641,7 @@ RESTORE → COMPACT → COMMAND → BUILD → RUN → SAVE → RESPOND → DONE
566
641
  npm test
567
642
  ```
568
643
 
569
- **229 tests · 40 files · all green.**
644
+ **323 tests · 49 files · all green.**
570
645
 
571
646
  ---
572
647
 
@@ -643,7 +718,13 @@ They represent different outcomes and safety defaults. <b>Home</b> groups read-o
643
718
  <details>
644
719
  <summary><b>Is the shell tool sandboxed?</b></summary>
645
720
  <br>
646
- On macOS, yes — every <code>shell</code> tool invocation is wrapped in <code>sandbox-exec</code> with a profile that <i>denies network access</i> and allows file writes only inside <code>cwd</code>, <code>/tmp</code>, and <code>/var</code>. Linux and Windows sandboxing is planned.
721
+ On macOS, commands use <code>sandbox-exec</code>; on Linux, restrictive network policies use Bubblewrap when installed. Windows has no supported subprocess network sandbox yet, so restrictive policies fail closed instead of silently running unrestricted. The native command runner itself works on all three platforms.
722
+ </details>
723
+
724
+ <details>
725
+ <summary><b>Which operating-system shells are supported?</b></summary>
726
+ <br>
727
+ Linux and macOS commands run through <code>/bin/sh</code>; Windows commands run through the system <code>ComSpec</code> (<code>cmd.exe</code> by default). Full native command lines support pipes, redirects, and conditional operators. The split <code>command</code> + <code>args</code> form quotes executable paths and arguments for the host shell.
647
728
  </details>
648
729
 
649
730
  <details>
@@ -681,7 +762,7 @@ Contributions welcome. The codebase is intentionally small and surgical — see
681
762
  ```sh
682
763
  git clone https://github.com/arthurpanhku/dvalincode
683
764
  cd dvalincode && npm install
684
- npm test # 65/65 ✅
765
+ npm test # 323/323 ✅
685
766
  npm run typecheck
686
767
  ```
687
768
 
@@ -745,3 +826,21 @@ Full source references: [docs/REFERENCES.md](docs/REFERENCES.md)
745
826
  </picture>
746
827
  </a>
747
828
  </p>
829
+
830
+ ---
831
+
832
+ ## 💛 Thanks to Our Contributors
833
+
834
+ <p align="center">
835
+ Every issue, idea, documentation improvement, test, and code contribution helps make DvalinCode better.
836
+ </p>
837
+
838
+ <p align="center">
839
+ <a href="https://github.com/arthurpanhku/dvalincode/graphs/contributors">
840
+ <img src="https://contrib.rocks/image?repo=arthurpanhku/dvalincode" alt="DvalinCode contributors">
841
+ </a>
842
+ </p>
843
+
844
+ <p align="center">
845
+ <sub>Want to join them? Read the <a href="CONTRIBUTING.md">contribution guide</a> and send your first pull request.</sub>
846
+ </p>