OPEN SOURCE / MIT Trust starts with inspection
The verifier
is open.
MaruCheck judges whether code has enough evidence to ship. You should be able to read how that judgment is made, run it locally, and change it with the community.
01 — RUN THE SAME VERIFIER
No black-box gate between your code and release.
$ npm install --save-dev --save-exact marucheck@0.3.0$ npx --no-install maru verify --diff02 — TWO REPOSITORIES / ONE PROOF LOOP
Separate release cycles. Shared contracts.
The local CLI and hosted application remain independent projects so either can evolve without hiding the boundary between local execution and shared evidence.
03 — CONTRIBUTE TO THE FAILURE PATH
Bring the case the happy path missed.
Report a false pass. Tighten a contract rule. Add an adapter. Improve the evidence a developer sees when a release is blocked. Focused issues and pull requests are welcome.