Use Claude, Anthropic's AI assistant, right from your terminal. Claude can understand your codebase, edit files, run terminal commands, and handle entire workflows for you.
Assist
staff0rd · App
A CLI tool for enforcing determinism in LLM development workflow automation.
Not claimed by its maker. Is this yours? Prove it and answer the findings
The registry now serves 0.747.2. Everything measured on this page describes 0.689.5.
Findings, provenance and the install command are records of the scanned version, not the one npm would give you today. Treat them as history until this listing is rescanned. Registry checked 2026-10-02.
What else was checked
Publisher and name
Nothing found across 5 checks run. Checked 2026-10-04.
Maintenance
MaintainedLast release 4 Oct 2026 (0.768.4), 0 days before this check on 4 Oct 2026.
Read from the npm registry's publish history, read by the nightly publisher check.
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 (pi/advice.ts:1)
- synchronous shell execution (pi/advice.ts:6)
- node child_process (pi/permission-gate.ts:1)
- synchronous shell execution (pi/permission-gate.ts:8)
- 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.
- Licence and provenance
- finding
- no LICENCE file at the root (.)
- Tool description integrity
- nothing to read
- Pattern set 1.0 matched nothing on 2026-10-04, but none of the descriptions the package ships runs to 120 characters, so there was little for a rule to read.
- It reads the descriptions the package ships, not what the server says when it runs, and a clean description is not the same thing as a safe tool.
- Row-level security
- nothing to read
- No Supabase migrations in the 19 files of the published package read on 2026-10-02, short of every file it ships: the nightly reading stops at 40 files or 4 MB, so there was nothing for this check to read.
- Not covered: A reading of files cannot prove a policy is enforced at run time: whether these migrations were applied, whether row-level security was switched on another way (the dashboard, SQL run by hand), or what a table holds. A database only the app's own server can reach (SQLite, or Postgres behind a server that holds the only connection) needs no row-level security for this reason, and its migrations are not read.
- Object-level authorisation
- nothing to read
- No Supabase migrations in the 19 files of the published package read on 2026-10-02, short of every file it ships: the nightly reading stops at 40 files or 4 MB, so there was nothing for this check to read.
- Not covered: Whether the app means every account to edit everything (an admin tool whose only account is its owner's), whether sign-up is open (a dashboard setting), and anything about a policy whose expression looks at the row. Whether the migrations were applied is not known. Policies that let anyone read every row are not counted here.
- CORS configuration
- 1 file
- Warning: server code in 1 file answers every origin. Where is withheld.
- App check set 1.0, 19 files of the published package read on 2026-10-02, short of every file it ships: the nightly reading stops at 40 files or 4 MB.
- Not covered: Whether it matters. A server that checks a token sent in a header gives a foreign page nothing it could not do without the browser, and a server bound to the loopback address is reachable only from pages open on the same machine (which is still every page that machine opens). A value chosen at run time, such as a variable that falls back to *, is not read: the hand count found one such server, and it is not in the figure.
- Not covered: Whether the server reads cookies at all, whether the echo is guarded by a check this reading does not follow, and anything decided at run time.
- No shipped credentials
- no match, 19 files read
- App check set 1.0 matched no credential in a format it recognises, bundles included, across the 19 files of the published package read on 2026-10-02, short of every file it ships: the nightly reading stops at 40 files or 4 MB.
- Not covered: Whether a key still works (none is ever tried, because trying one would be using it), credentials in formats the check does not name, anything in a repository's history, and files the nightly reading does not reach when a package is over its caps.
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.
Tool descriptions are read with pattern set v1.0, published with every rule, its sources and how often it has been wrong.
App checks are read with app check set v1.0, published with every rule, what it does not cover and how often it has been wrong.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
What it does
A CLI tool for enforcing determinism in LLM development workflow automation.
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 0.689.5, the file with digest sha512-pnrTFObQo2q8p3Lu6I2ZrBjzbOQ6XSiXzEh9Gunsa6aDVwIEOZy7VSY+23APDwdGAq+baQxyp9Rn1VRP798QWQ==, 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 -p @staff0rd/assist@0.689.5 aPinned to 0.689.5, 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.
41,253 installs last month · build provenance signed · no published advisories · checked 2026-10-02
Where this came from
- Registry
- npm
- Package
- @staff0rd/assist
- Version read
- 0.689.5
- Resolved
- 2026-09-23
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/staff0rd/assist
- Commit
- d9b618aad08a
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-09-23
- Checked
- 2026-09-23
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/staff0rd-assist)About this listing
- Kind
- App
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-09-23
Similar apps
All appsVerification 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.