3 findingsStatic scanned
Runs OpenAI's Codex coding agent locally on your computer from the command line.
71.3M installs/moApache-2.0
Flow Agents
kontourai · Agent
Flow Agents installs workflow skills and hooks into the coding agent tools you already use. It takes work from idea through plan, build, review and verification to release, and records acceptance criteria, evidence and handoffs in your project so a later session can resume from that state instead of chat memory. Work is expected to end with evidence such as tests, CI results or review findings, or an explicit note that it was not verified.
Written by ooruby from the README of @kontourai/flow-agents 6.5.2.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Agents can drift, skip checks and call partial work done, and this records where the work stands and what evidence backs it.
What you could do with it
- Have your agent take a feature through its plan, build, review and verify skills, with each step recorded.
- Resume a half-finished task in a new session from the recorded plan and evidence instead of chat history.
- Have format and lint checks run automatically after each file your coding agent edits.
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 (src/external-lifecycle-authority.ts:4)
- synchronous shell execution (src/external-lifecycle-authority.ts:547)
- node child_process (src/tools/build-universal-bundles.ts:2)
- node child_process (src/tools/build-universal-bundles.ts:444)
- 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.
Corrected after a reading by hand on 2026-10-10
- No shipped credentials: the automated note “The scan matched 6 credential-shaped strings in the published files. Location withheld pending disclosure to the maker.” was withdrawn. Test values throughout its tests: fixture tokens and made-up secrets used to check that its logs and snapshots leave them out.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Flow Agents keeps coding agents on track with evidence-backed workflows — a Kontour product that applies Flow and Veritas process discipline as a portable layer inside the agent tools you already use: Claude Code, Codex, Kiro, opencode, and pi — with fram
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 6.5.2, the file with digest sha512-zOUIdMMz3pqe6M+Bn/HkngIIr/Rg+ORlrApfXK+UMijwQy99BaPG/SAx7+fymXnc6eWh5xRei8d+zVRN5r5rNA==, 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 @kontourai/flow-agents@6.5.2 flow-agentsPinned to 6.5.2, 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
- @kontourai/flow-agents
- Version read
- 6.5.2
- Resolved
- 2026-10-09
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/kontourai/flow-agents
- Commit
- cde7505db161
- 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/kontourai-flow-agents)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-09
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.