Reads a build agent's log and flags repeated errors, repeated edits and files outside its scope.
Ticket Prune
adlc · Agent
Ticket prune keeps the ADLC ticket store from filling up with finished work. It reports tickets it can determine are stale, using an explicit status field such as done, shipped or archived or, if you ask, by checking that every scope a ticket declares already exists on a base ref. Nothing changes until you pass the write flag, and then a legacy ticket file is marked completed in place while a sharded store archives the ticket.
Written by ooruby from the README of @adlc/ticket-prune 1.12.0.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Completed tickets stop posing as open backlog, so you can tell live work from leftovers without checking each by hand.
What you could do with it
- Run it with no flags to list the tickets that look finished without changing the ticket store.
- Turn on scope inference so a ticket counts as stale when all its declared scope globs match tracked files on a base ref.
- List stale tickets that still freeze rails, then complete them one id at a time with the ticket complete command.
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
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
Reports and archives stale/shipped tickets out of .adlc/tickets.json (dry-run by default).
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 1.12.0, the file with digest sha512-B713d5UljW5bkDnkyY739lXyMw2fSZbCdLSywtIdr6vc1lOwZ12HKxNkJAZz1wXfkF3YNhk5RSuZjnTzlnRYfA==, 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 @adlc/ticket-prune@1.12.0Pinned to 1.12.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
- @adlc/ticket-prune
- Version read
- 1.12.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/voodootikigod/adlc
- Commit
- bddae80871bf
- 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/adlc-ticket-prune)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-10
More from adlc
See the storefrontRuns ready tickets in parallel through Claude Code workers, then gates and merges the results.
Checks that a ticket is self-contained before a build agent starts, by asking a model what is missing.
Similar 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.