3 findingsStatic scanned
Runs OpenAI's Codex coding agent locally on your computer from the command line.
71.3M installs/moApache-2.0
Storybloq
storybloq · Agent
Storybloq gives Claude Code and Codex a project memory that lives in your repository: tickets, issues, handovers, lessons and review evidence, so each session starts where the last one left off. Hooks inject a resume prompt at session start, including after compaction. For Claude Code it also records usage-limit stops and resumes the session after the reset, and a library can load project data in code.
Written by ooruby from the README of @storybloq/storybloq 1.15.9.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Work on a project carries across sessions and usage limits instead of stopping with the conversation that started it.
What you could do with it
- Set up a project, then let each new session read the handover the previous one left.
- Leave overnight autonomous work running and have a session that hit a usage limit resume after the reset.
- Check the queue of pending auto-resumes, cancel one or requeue a record that was stood down.
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
Project memory for Claude Code and Codex. Storybloq stores tickets, issues, handovers, and lessons in a .story/ folder inside your repo so every session starts where the last one left off. Pairs with the Storybloq Mac app on the App Store.
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.15.9, the file with digest sha512-MVKmzn0fZepJblRmAmc44CFk1aUZoD8FP+c9U4H1r8LzWPC9hmnQTxgTmyHo2vvrj4dKOwEsBbXkHH35x6E7aw==, 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 @storybloq/storybloq@1.15.9 storybloqPinned to 1.15.9, 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
- @storybloq/storybloq
- Version read
- 1.15.9
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
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/storybloq-storybloq)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-04
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.