Menghasilkan laporan penerimaan read-only untuk perubahan Git guna memverifikasi apa yang telah dimodifikasi dan pengecekan apa saja yang telah dijalankan oleh AI agent.
Juga dikenal sebagai 2648782102/proofpack-cli, proofpack-cli
- Stars
- 1
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- 0.3.2
- Commit terakhir
- 9 Nov 2026
- Lisensi
- MIT
Apa itu Proofpack MCP?
Menghasilkan laporan penerimaan read-only untuk perubahan Git guna memverifikasi apa yang telah dimodifikasi dan pengecekan apa saja yang telah dijalankan oleh AI agent.
Ringkasan dibuat dari README proyek
Tentang Proofpack MCP server
Proofpack menyediakan bukti penerimaan (evidence receipt) bagi developer untuk perubahan kode yang dilakukan oleh AI agent. Tool ini menghasilkan laporan penerimaan read-only yang merinci apa yang dapat dilihat oleh Git, pengecekan spesifik apa saja yang telah dijalankan, dan tugas mana yang belum terverifikasi. Tool ini membantu Anda mengonfirmasi secara tepat apa yang telah dimodifikasi dan pengujian apa yang sebenarnya terjadi setelah tugas coding selesai.
Server ini berjalan secara lokal sebagai subprocess yang diluncurkan oleh host melalui entrypoint proofpack-mcp stdio, tanpa memerlukan akun, layanan cloud, atau API model. Saat digunakan melalui host MCP, tool ini menyediakan satu tool proofpack_check yang melakukan inspeksi Git secara read-only untuk menghasilkan laporan Markdown atau JSON tanpa mengeksekusi perintah proyek atau menulis file. Bagi pengguna yang menjalankan CLI secara langsung, tool ini dapat mengeksekusi perintah tertentu menggunakan flag --run, yang menggunakan shell lokal dan hak akses user.
Berbeda dengan automated tester, Proofpack tidak mengklaim bahwa sebuah perubahan sudah benar atau aman untuk di-merge. Fokus utamanya adalah memisahkan fakta yang teramati dari prompt heuristik dan pekerjaan yang belum diperiksa, guna memastikan developer mengetahui batasan dari verifikasi yang dilakukan.
Apa yang bisa Anda lakukan dengannya
- 1Verifikasi perubahan kode AIHasilkan laporan untuk melihat file mana saja yang dimodifikasi dan bagaimana ringkasan diff setelah agent menyelesaikan sebuah tugas.
- 2Dokumentasikan perintah test yang dijalankanJalankan suite test tertentu dan catat status exit serta durasi waktunya dalam laporan penerimaan formal.
- 3Identifikasi area kode yang belum di-testTentukan bagian mana dari proses pengembangan, seperti linting atau audit dependency, yang terlewat selama sesi berlangsung.
- 4Bagikan hasil verifikasi yang telah disanitasiBuat versi laporan yang aman dengan menghapus path sensitif dan teks perintah sebelum membagikannya kepada orang lain.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal Proofpack MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal Proofpack MCP di Claude Code
$ claude mcp add proofpack-cli -- npx -y proofpack-cliInstal Proofpack MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"proofpack-cli": {
"command": "npx",
"args": [
"-y",
"proofpack-cli"
]
}
}
}Instal Proofpack MCP di VS Code
.vscode/mcp.json
{
"servers": {
"proofpack-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"proofpack-cli"
]
}
}
}Instal Proofpack MCP di VS Code CLI
$ code --add-mcp '{"name":"proofpack-cli","type":"stdio","command":"npx","args":["-y","proofpack-cli"]}'Instal Proofpack MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"proofpack-cli": {
"command": "npx",
"args": [
"-y",
"proofpack-cli"
]
}
}
}Instal Proofpack MCP di Codex
$ codex mcp add proofpack-cli -- npx -y proofpack-cliInstal Proofpack MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.proofpack-cli] command = "npx" args = ["-y", "proofpack-cli"]
Instal Proofpack MCP di Gemini CLI
$ gemini mcp add -s user proofpack-cli npx -- -y proofpack-cliInstal Proofpack MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"proofpack-cli": {
"command": "npx",
"args": [
"-y",
"proofpack-cli"
]
}
}
}Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkau2648782102/proofpack-cli is public and reachablegithub.com/2648782102/proofpack-cli ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyaproofpack-cli names 2648782102/proofpack-cli as sourcenpmjs.com/package/proofpack-cli ↗Lolos
- Provenance build (atestasi Sigstore)No build attestation published for this releaseTidak diperiksa
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-11-09github.com/2648782102/proofpack-cli ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerNo popular package one edit away from proofpack-cliLolos
- Tidak ada advisory kritis pada paket atau dependensinya1 resolved dependencies checked; no critical advisoryosv.dev ↗Lolos
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPTidak diperiksa
README
Lihat di GitHubProofpack
An evidence receipt for AI-assisted code changes.
After a coding agent says "done", Proofpack shows what Git can see, which checks actually ran, and what remains unchecked. It runs locally, needs no account, and never gives a "safe to merge" verdict.
npx -y --package=proofpack-cli@0.3.2 proofpack check --run "npm test"
The command prints a Markdown report to stdout. Default inspection is read-only; npm test runs only because it was explicitly supplied with --run.
## Change
- Git-visible files: 2
- Diff summary: 18 insertions · 2 deletions
## Checks
- Explicit commands requested: 1
- Observed outcomes: 1 passed · 0 failed · 0 not run
- npm test: passed · exit 0
## Not checked
- Lint, build, dependency audits, and runtime behavior were not run.
Repository: 2648782102/proofpack-cli · npm: proofpack-cli · Release: v0.3.2
What it is for
Proofpack helps an individual developer answer three questions after a coding task: what changed, what checks actually ran, and what remains unchecked. It records Git change facts, explicit command evidence, and heuristic review prompts; it does not claim that a change is correct.
The report separates observed facts, heuristic prompts, and unchecked work. A passing command is evidence of that invocation only.
Product principles
- One command, one readable report.
- Local by default; no account, daemon, model API, or upload.
- Observed facts, heuristic prompts, and unchecked work are separated.
- No project command runs unless the user explicitly supplies
--run. - Git inspection is read-only; explicitly run commands use the user's shell and privileges without a sandbox.
Current distribution shapes
The 0.3.2 package contains both the proofpack CLI and the proofpack-mcp stdio entrypoint. MCP is a host-launched local subprocess, not a cloud service or a host plugin. See docs/MCP.md for the protocol contract and host configuration.
MCP quick start
After installing the package in a project, configure an MCP host to launch the local binary:
{
"mcpServers": {
"proofpack": {
"command": "npx",
"args": ["-y", "--package=proofpack-cli@0.3.2", "proofpack-mcp"]
}
}
}
The host then sees one read-only proofpack_check tool. It generates a Markdown or JSON acceptance report without executing project commands or writing files.
Install and first use
Use npm without a global install:
npx -y --package=proofpack-cli@0.3.2 proofpack check
Or install the package in a project:
npm install --save-dev proofpack-cli@0.3.2
npx proofpack check
The CLI binary is named proofpack; the MCP binary is named proofpack-mcp.
This prints a Markdown report to stdout without changing the working tree, running project commands, or making network requests. To save it, pass an explicit path:
npx -y --package=proofpack-cli@0.3.2 proofpack check --output .proofpack/review.md
Explicit checks
npx -y --package=proofpack-cli@0.3.2 proofpack check --run "npm test" --run "npm run lint"
npx -y --package=proofpack-cli@0.3.2 proofpack check --run "npm test" --format json
npx -y --package=proofpack-cli@0.3.2 proofpack check --run "npm test" --format markdown,json --output .proofpack/review.md
Each command is previewed before execution, run sequentially from the repository root through the user's shell, and recorded with timing, exit status, bounded stdout/stderr, truncation, and best-effort redaction. --timeout <seconds> defaults to 120 and applies per command. Multiple formats require --output and write sibling .md / .json files.
Commands are not sandboxed and can modify the working tree. Review every command and its output before sharing a report. Passing checks are evidence of those invocations only, not proof of correctness or security.
Branch/base and sharing
npx -y --package=proofpack-cli@0.3.2 proofpack check --base main
npx -y --package=proofpack-cli@0.3.2 proofpack check --run "npm test" --share-safe --output .proofpack/share.md
npx -y --package=proofpack-cli@0.3.2 proofpack check --output .proofpack/review.md --open
To render the report in Simplified Chinese, pass --lang zh-CN or set PROOFPACK_LANG=zh-CN. The default is English. This changes Markdown and JSON text fields only; schema keys, status values, paths, command stdout, and rule IDs stay unchanged.
npx -y --package=proofpack-cli@0.3.2 proofpack check --lang zh-CN
--base compares committed, staged, and working-tree changes against a resolved Git ref and excludes untracked files from that view. --share-safe omits branch, HEAD, base commit, file paths, output destination, command text, command output, and prompt evidence from both Markdown and JSON; status, counts, timings, and limitations remain. --open is opt-in, requires a written Markdown report, and uses the system opener. It never uploads the report.
Review even share-safe reports before sharing: omission is best-effort and aggregate metadata may still be sensitive.
What it does not do
Proofpack does not discover or run package scripts automatically, infer test or build results, review code with an AI, assign a correctness score, approve changes, upload reports, collect telemetry, or sandbox explicit --run commands. Commands supplied with --run use the current user's shell and privileges.
The MCP adapter is narrower still: its single proofpack_check tool performs read-only Git inspection and does not execute project commands, write report files, open applications, make network requests, or invoke a model.
Early development: repository-local init, sandboxed execution, CI-result import, and agent-trace import are not implemented. See roadmap and MCP contract.
Development
Requirements: Node.js 24 or newer.
npm install
npm run dev -- check
npm run check
npm test
npm run build
Documents
- Product requirements
- User experience
- CLI contract
- MCP contract
- Architecture
- Security and privacy
- Open-source references
- Roadmap
- Development handoff
- Release checklist
- 0.3.1 release notes
- 0.3.2 release notes
- Distribution and promotion
- 30-second demo script
- Changelog
- Decisions
License
MIT. See LICENSE.
Pertanyaan tentang Proofpack MCP
Bagaimana cara menambahkan Proofpack MCP ke Claude Code?
Jalankan claude mcp add proofpack-cli -- npx -y proofpack-cli di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan Proofpack MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Apakah Proofpack mengeksekusi perintah proyek melalui MCP?
Tidak, adapter MCP terbatas pada inspeksi Git secara read-only dan tidak mengeksekusi perintah proyek, menulis file, atau melakukan request jaringan.
Apakah Proofpack merupakan layanan cloud?
Bukan, ini adalah tool lokal yang berjalan sebagai subprocess yang diluncurkan oleh host dan tidak memerlukan akun atau koneksi cloud.
Apakah Proofpack menjamin bahwa perubahan kode sudah benar?
Tidak, tool ini hanya memberikan bukti tentang apa yang berubah dan perintah apa yang dijalankan; tool ini tidak menjamin kebenaran kode atau memberikan vonis aman untuk di-merge.
Bisakah saya menjalankan test tertentu dengan Proofpack?
Ya, Anda dapat menggunakan flag --run untuk menyertakan perintah secara eksplisit seperti npm test agar dicatat di dalam laporan.