100%
Every launch manifest type has a verified package path: skill, MCP server, tool bundle, agent profile, workflow pack, eval pack, policy pack and adapter.
Launch
Nipmod is technically live. The public paths are ready; ecosystem maturity is earned from external users, external package authors and independent reviewers running the same proof paths.
Readiness
Every launch manifest type has a verified package path: skill, MCP server, tool bundle, agent profile, workflow pack, eval pack, policy pack and adapter.
Trust model, catalog matrix, production gates, restore drill, proof transcript, review packet generator and known risks are reproducible.
First user, package author, repo owner, reviewer and agent host paths are ready. Real adoption evidence is tracked separately.
External Proof
Public source, launch demo, founder post, founder DM and non endorsement language are ready.
Needs a Gitlawb founder or maintainer response.
Review packet, gates, proof loop, threat model and sign off template are ready.
Needs an independent reviewer signature or published findings.
First user loop, author dry run, repo package patch preview and receipt template are ready.
Needs external redacted user receipts. Current ledger count is zero.
Verified first party packages cover every launch manifest type.
Needs external package authors accepted into the registry.
Install, run doctor, search, inspect, install into a workspace and audit a verified package.
curl -fsSLO https://nipmod.com/install.sh && bash install.sh
nipmod doctor --online
nipmod search gitlawb --online
mkdir -p nipmod-demo && cd nipmod-demo
nipmod inspect pkg:did:key:z6MkqDAkKNtWH69ZYoFitErk1CCKofFP5AaFjVXy5bVQ4fbD/gitlawb-repo-reader@0.1.0
nipmod install pkg:did:key:z6MkqDAkKNtWH69ZYoFitErk1CCKofFP5AaFjVXy5bVQ4fbD/gitlawb-repo-reader@0.1.0
nipmod install
nipmod outdated
nipmod audit --onlineUse this when a reviewer wants to verify the installer before execution.
curl -fLO https://nipmod.com/install.sh
curl -fLO https://nipmod.com/install.sh.sha256
shasum -a 256 -c install.sh.sha256
bash install.shCreate a Gitlawb package draft and produce the registry candidate before any public index decision.
nipmod init --name gitlawb-demo-package --dir gitlawb-demo-package
cd gitlawb-demo-package
nipmod manifest validate --dir .
nipmod publish . --dry-run --jsonReview the source, production gates, load smoke, supply chain check and known limitations.
node tools/verify-all.mjs --prod
node tools/prod-load-smoke.mjs --profile launch
node tools/supply-chain-check.mjsSearch multiple registry indexes while failing closed on conflicting package digests.
nipmod search policy --registries https://nipmod.com/registry/packages.json,https://mirror.example/packages.jsonFounder Review
Gitlawb gives agents decentralized source.
Nipmod is the package layer: signed bundles, DID publisher identity, pinned installs, public advisories and witness backed audit.
Independent project asking for Gitlawb review, not claiming endorsement.
Run the demo and send the strongest objection.
Public demo: https://nipmod.com/launch
Source: https://gitlawb.com/node/repos/z6Mkwbud/nipmodWe built Nipmod as an independent package layer for Gitlawb agents. It keeps Gitlawb as decentralized source and adds verification around install: signed bundles, DID publisher identity, pinned lockfiles, public advisories and witness backed audit.
Could you sanity check whether this model fits Gitlawb, should stay independent, or should become a smaller primitive Gitlawb exposes directly?Persona:
Commands run:
Package:
Result:
Blocker:
May quote anonymously: yes or no
Redacted output:Truth
The path exists. This line reaches 100 only with external people or signed review evidence.
The path exists. This line reaches 100 only with external people or signed review evidence.
The path exists. This line reaches 100 only with external people or signed review evidence.
The path exists. This line reaches 100 only with external people or signed review evidence.
The path exists. This line reaches 100 only with external people or signed review evidence.