Operations — in progress
xops detects the supported tools in your Node.js repo — package managers, git, workspaces, tests, quality checks, release tools, dependency monitoring, security scanners, secrets, CI, API assets, MaGit, utilitix, Docker, deployment, and observability — then gives humans and code agents one safe way to understand and act.
The new story
xops started with the release problem. A real release is bigger than npm publish — package discovery, dependency order, build/test gates, version handling, publish safety, git push coordination, exit codes, journaling, recovery. That is what xops already made safe.
But the same problem now exists across the rest of the repository. A modern Node.js repo is not operated by one tool. It is operated through package managers, git, workspaces, tests, quality checks, release tools, dependency bots, security scanners, secret providers, CI workflows, API collections, metadata stores, Docker files, deployment configs, observability hooks, and sometimes code agents trying to run all of it without getting stuck.
Start read-only
xops ops status is the map of the repo. It does not install anything, write configs, initialize tools, or connect services. It reads the repository and reports what exists.
Detected areas
Native ownership
xops does not make the toolchain disappear. npm still installs. git still stores history. Renovate and Dependabot still manage dependency updates. Vitest and Playwright still run tests. MaGit still owns Mongo metadata versioning. utilitix still owns Mongo utility operations. xops connects them into one operating contract.
One operation, two audiences
xops returns both.