bytematch
cognis-digital/bytematch
Verifies that deployed on-chain bytecode matches a given source/Foundry build, detecting unverified or tampered proxies and implementations.
Instalação
npx convez-ai cognis-digital/bytematch1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
README
A tradução para o português deste README ainda está na fila.
BYTEMATCH
Verifies that deployed on-chain bytecode matches a given source/Foundry build, detecting unverified or tampered proxies and implementations.
Web3 & Smart-Contract Security — on-chain safety and analytics.
pip install cognis-bytematch
bytematch scan . # → prioritized findings in seconds
Usage — step by step
bytematch verifies that deployed EVM runtime bytecode matches a build artifact.
- Install (from a clone or release):
pip install -e . - Verify deployed bytecode against a compiler artifact (Hardhat/Foundry JSON, raw hex, a file, or
-for stdin):
Or compare two raw hex blobs directly:bytematch verify --deployed 0x6080... --artifact build/MyContract.jsonbytematch verify --deployed deployed.hex --artifact-hex artifact.hex - Tighten the comparison with
--strictto fail on any difference (including metadata/immutables):bytematch verify --deployed 0x6080... --artifact build/MyContract.json --strict - Read the result as machine-readable JSON for tooling:
The command exits non-zero on a mismatch, so the exit code alone gates a pipeline.bytematch --format json verify --deployed 0x6080... --artifact build/MyContract.json - Automate in CI (e.g. post-deploy supply-chain check):
- run: bytematch verify --deployed "$DEPLOYED_HEX" --artifact build/MyContract.json --strict
Contents
- Why bytematch? · Features · Quick start · Example · Architecture · AI stack · How it compares · Integrations · Install anywhere · Related · Contributing
Why bytematch?
Decentralized 'is this contract actually what its repo claims' check that runs in CI/CD — supply-chain integrity for on-chain code.
bytematch is single-purpose, scriptable, and self-hostable: point it at a target, get prioritized results in the format your workflow already speaks (table · JSON · SARIF), gate CI on it, and let agents drive it over MCP.
Features
- ✅ Keccak256
- ✅ Normalize Bytecode
- ✅ Split Metadata
- ✅ Strip Metadata
- ✅ Extract Metadata
- ✅ Verify
- ✅ Load Artifact Runtime Bytecode
- ✅ Verify Artifact
- ✅ Runs on Linux/macOS/Windows · Docker · devcontainer
- ✅ Ports in Python, JavaScript, Go, and Rust (
ports/)
Quick start
pip install cognis-bytematch
bytematch --version
bytematch scan . # scan current project
bytematch scan . --format json # machine-readable
bytematch scan . --fail-on high # CI gate (non-zero exit)
Example
$ bytematch scan .
[HIGH ] BYT-001 example finding (./src/app.py)
[MEDIUM ] BYT-002 another signal (./config.yaml)
2 findings · risk score 5 · 38ms
Architecture
flowchart LR
IN[binary / sample] --> P[bytematch<br/>scan + match]
P --> OUT[detections]
Use it from any AI stack
bytematch is interoperable with every popular way of using AI:
- MCP server —
bytematch mcp(Claude Desktop, Cursor, Cognis.Studio, uncensored-fleet) - OpenAI-compatible / JSON — pipe
bytematch scan . --format jsoninto any agent or LLM - LangChain · CrewAI · AutoGen · LlamaIndex — wrap the CLI/JSON as a tool in one line
- CI / scripts — exit codes + SARIF for non-AI pipelines
How it compares
| Cognis bytematch | Sourcify | |
|---|---|---|
| Self-hostable, no account | ✅ | varies |
| Single command, zero config | ✅ | ⚠️ |
| JSON + SARIF for CI | ✅ | varies |
| MCP-native (AI agents) | ✅ | ❌ |
| Polyglot ports (JS/Go/Rust) | ✅ | ❌ |
| Open license | ✅ COCL | varies |
Built in the spirit of Sourcify, re-framed the Cognis way. Missing a credit? Open a PR.
Integrations
Pipes into your stack: SARIF for code-scanning, JSON for anything, an MCP server (bytematch mcp) for AI agents, and a webhook forwarder for SIEM/Slack/Jira. See docs/INTEGRATIONS.md.
Install — every way, every platform
pip install "git+https://github.com/cognis-digital/bytematch.git" # pip (works today)
pipx install "git+https://github.com/cognis-digital/bytematch.git" # isolated CLI
uv tool install "git+https://github.com/cognis-digital/bytematch.git" # uv
pip install cognis-bytematch # PyPI (when published)
docker run --rm ghcr.io/cognis-digital/bytematch:latest --help # Docker
brew install cognis-digital/tap/bytematch # Homebrew tap
curl -fsSL https://raw.githubusercontent.com/cognis-digital/bytematch/main/install.sh | sh
| Linux | macOS | Windows | Docker | Cloud |
|---|---|---|---|---|
scripts/setup-linux.sh | scripts/setup-macos.sh | scripts/setup-windows.ps1 | docker run ghcr.io/cognis-digital/bytematch | DEPLOY.md (AWS/Azure/GCP/k8s) |
Related Cognis tools
reentryx— Static + symbolic detector that flags reentrancy, cross-function, and read-only reentrancy paths in Solidity/Vyper with CI-gating SARIF output.forkfuzz— Mainnet-fork invariant fuzzer that replays your contract against live state and stateful sequences to break protocol invariants before deploy.approvewarden— Scans any wallet for dangerous ERC-20/721/1155 token approvals and infinite allowances, scoring drainer exposure and emitting revoke transactions.mevscope— Replays a tx or address history to attribute sandwich, frontrun, and backrun MEV extraction with per-trade loss accounting.rugradar— Token contract risk scanner detecting honeypots, hidden mint/blacklist functions, owner backdoors, and unlocked liquidity before you ape.storagelens— Diffs and decodes contract storage layouts across proxy upgrades to catch storage-collision and uninitialized-slot bugs.
Explore the suite → 🗂️ all 170+ tools · ⭐ awesome-cognis · 🔗 cognis-sources · 🤖 uncensored-fleet · 🧠 engram
Contributing
PRs, new rules, and demo scenarios are welcome under the collaboration-pull model — see CONTRIBUTING.md and SECURITY.md.
⭐ If
bytematchsaved you time, star it — it genuinely helps others find it.
Interoperability
{} composes with the 300+ tool Cognis suite — JSON in/out and a shared
OpenAI-compatible /v1 backbone. See INTEROP.md for the
suite map, composition patterns, and reference stacks.
License
Source-available under the Cognis Open Collaboration License (COCL) v1.0 — free for personal, internal-evaluation, research, and educational use; commercial / production use requires a license (licensing@cognis.digital). See LICENSE.