5 findingsStatic scanned
Volter Ztrack
volter · Agent
ztrack works like a type checker for your issue tracker: a checked acceptance criterion has to cite a commit that exists in git, plus the evidence and proof the preset requires. Run it on demand in CI, or let its loop hold your AI coding agent's turn until the work passes. By default it confirms the commit exists, not that it is relevant, though a criterion can name the paths a commit must touch. It can sync with GitHub Issues or import tasks from Markdown.
Written by ooruby from the README of @volter/ztrack 2.5.0.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
AI coding agents can close tickets on prose alone, and this makes each done claim cite a commit that really exists, with proof.
What you could do with it
- Add a check to CI so a ticket fails when an acceptance criterion cites a commit hash that does not exist.
- Start a loop on one issue so your agent's turn is held until every criterion has evidence and passes.
- Pull in your GitHub Issues and keep GitHub as the source of truth while ztrack checks them.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- node child_process (visualizer/client/render.e2e.test.tsx:20)
- synchronous shell execution (visualizer/client/render.e2e.test.tsx:32)
- node child_process (visualizer/client/render.viz13.e2e.test.tsx:23)
- synchronous shell execution (visualizer/client/render.viz13.e2e.test.tsx:37)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
A typechecker for your issue tracker — every checked acceptance criterion must cite a real commit and proof, verified by `ztrack check` (and enforced on coding agents via a loop gate).
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 2.5.0, the file with digest sha512-MyhfmlDfo05dvXXXdeMk8iFfGW6nBZaSwBTTvjXAj8E2vsS1HtgpCuKpQF1iFwEbeWfZaBdqA064v7wTzaC/9w==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y @volter/ztrack@2.5.0Pinned to 2.5.0, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- @volter/ztrack
- Version read
- 2.5.0
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/volter-ai/ztrack
- Commit
- 10ebd7163c32
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/volter-ztrack)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-10
More from volter
See the storefrontSimilar agents
All agentsVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.