3 findingsStatic scanned
Runs OpenAI's Codex coding agent locally on your computer from the command line.
71.3M installs/moApache-2.0
Dev Loops
mfittko · Agent
Dev Loops runs a repeatable development loop on a GitHub issue. It normalises the issue, refines the spec, builds the change on a feature branch, runs review gates, resolves review threads on GitHub and merges the pull request. In auto mode it works on its own until a human approval checkpoint. The same loop is available as a Claude Code plugin, as a Pi extension and as a standalone command line tool. It needs the GitHub command line tool, installed and signed in.
Written by ooruby from the README of dev-loops 1.0.5.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
A GitHub issue is carried through refinement, build, review and merge without you steering each step by hand.
What you could do with it
- Ask for a dev loop on a GitHub issue in plain language and let it work up to the approval checkpoint.
- Run a time-boxed spike on a question before you commit to an implementation.
- Review a pull request by booting the app from an isolated worktree and driving the screens that changed.
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 (skills/docs/gate-review-sub-loop-contract.md:182)
- node child_process (skills/dev-loop/scripts/post-gate-verdict-fallback.mjs:25)
- node child_process (skills/dev-loop/scripts/post-gate-verdict-fallback.test.mjs:5)
- node child_process (scripts/refresh-test-timings.mjs:3)
- 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
Agent-harness-agnostic dev-loop infrastructure (Pi and Claude Code) for reusable local and remote development loops
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.0.5, the file with digest sha512-hfB/cFx1DI81Oit0zg79hLVVHOLtBi+3bIsMMnIGLe8AaOeyKWWfOFgF9XXFg5U734TpaYiIzqUQKnoNuZ4oEw==, 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 dev-loops@1.0.5Pinned to 1.0.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.
Where this came from
- Registry
- npm
- Package
- dev-loops
- Version read
- 1.0.5
- 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/mfittko/dev-loops
- Commit
- d8252e395fcc
- 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/dev-loops)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-06
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.