Packages should be the easy part.
Gritpack gets, locks and publishes packages for Rust, npm, Go, C and C++, installs command-line applications for you, and keeps signed records of who published what. This guide teaches it one step at a time, and the command reference comes straight from the program's own help.
$ curl -fsSL https://get.gritpack.org/install/gritpack | sh
$ gritpack init --dialect c/c23
$ gritpack add @ada/greet
$ gritpack sync --frozen
$ gritpack publish --dry-run
Three ways in
Start from what you are doing.
Using packages
A project manifest, a lock file and a packages directory. Add, sync, update and upgrade, with Cargo, npm and Go kept as they are.
Mental model → Projects → Lock filePublishing
A dry run first, then a publication that is all or nothing, a README and a licence on every version, and a signed receipt you can check later.
Your first package → Step by stepTeams and private hubs
Invitations and logins, scopes and owners, workspaces released together, evidence you can verify offline, and the commands a hub's administrator uses.
Logging in → Workspaces → AdministrationThe guide
Thirty-four chapters, in eleven parts.
Read it in order, or jump to your part. Each part ends by saying who is done and can stop there.
Start here
PATH, upgrades
3Your first five minutesSearch the public hub, look at a package, install an application, start a project
Using packages
gritpack.toml, init, add, remove, and the packages directory
6The lock file and syncgritpack.lock, sync, --frozen, --offline, and the download cache
7Keeping up to dateoutdated, update, upgrade, list, why, verify and doctor
8Finding packagessearch and info, deprecated and yanked versions
9Hubs and sourcesThe public hub, private hubs, which hub a package comes from, --hub and --from
Each ecosystem
Applications
gritpack install, app list, app upgrade, app which, uninstall
15Installers and download linksHow the installer works, download links, and building a download for your application
Publishing
pack, publish --dry-run, publish, and what the hub keeps
17README and licenceThe documentation every version needs, waivers, and licence rules
18After publishingVersions never change; yank, deprecate, and undo them
19Publishing step by stepPlans, verification, transactions, status, resume and abort
Accounts and teams
gritpack login, invitations, where the credential is kept, renewing before it expires
21Logins and profilesSeveral hubs, auth list, use, status, import, migrate, logout, revoke
22Names, scopes and ownersGlobal names, @scope/name, claiming a scope, who may publish what
Workspaces and releases
workspace init, status, graph, affected, verify
24Releasing a workspacerelease-plan, publishing members together, all or none
Trust
Scripting and automation
--json, --json=fields, --jq, NDJSON, JSON errors and exit codes
28Continuous integrationLogging in from CI, frozen installs, publishing without prompts
29Shell comfortsAliases, completion, the pager, help topics and environment variables
30Tools and agentsgritpack api, gritpack mcp, sources and graph for compilers and coding agents
Hub administration
When you need help
Command reference
Every command, subcommand and flag, generated from gritpack --help for this release, so it never drifts from the program.
Help topics
Environment variables, exit codes, JSON output and where logins are kept: the same text as gritpack help <topic>.
Troubleshooting
Start from the message you see, find the cause and the fix. gritpack doctor is usually the first step.