Zip Meta Map
This tool is in early development. APIs may change.
🧪 Concept Prototype
Not packaged yetThis tool is in early design. You can explore the source code or contribute to its development.
What exists today:
- CI Pipeline
- Project Structure
- Design Spec
Make repos and ZIPs self-describing for LLMs with CI-grade diffs.
Turn any ZIP or folder into an LLM-friendly metadata bundle — role-classified files, traversal plans, byte budgets
Good for
- CI gating with diff --exit-code (246 tests, JSON Schema-validated)
- LLM agents that need repo maps under token budgets
- Deterministic builds: same repo = same index, diffable in CI
- GitHub Actions with step summaries and PR comments built in
Not for
- Replacing code search or embeddings (it complements them)
- Runtime vulnerability scanning (heuristics, not CVEs)
Verified claims
- ✓
Given the same repository state, zip-meta-map produces byte-identical index output.
- ✓
The test suite contains 246 passing tests covering CLI, schema validation, and diff behavior.
- ✓
zip-meta-map diff --exit-code returns non-zero when metadata drifts, suitable for CI gating.
- ✓
LLM plans respect configurable token budgets, producing structured context that fits within specified limits.
- ✓
All output conforms to a published JSON Schema, validated in CI on every commit.
Aspirational
1
- ○
Typical repo builds complete in under one second on commodity hardware.
Anecdotally true but not yet benchmarked with reproducible methodology.
Not for
- Does not replace code search or embeddings — it complements them with structural metadata.
- Does not perform runtime vulnerability scanning — heuristic flagging is advisory, not CVE-grade.
- Does not require or assume any specific LLM provider — output is plain JSON consumable by any tool.