npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@rogeriohsjr/nodulus

v2.5.0

Published

An open-source TypeScript CLI for LLM workflows with validated artifacts and resumable execution.

Readme

Nodulus

An open-source TypeScript CLI for LLM workflows with validated artifacts and resumable execution.

Install the public npm package with Node.js 24:

npm install --global @rogeriohsjr/nodulus@latest
nodulus --version
nodulus --help

For project setup and usage, see the Nodulus user guide.

Status: folders 00 through 08 are implemented and independently reviewed: initialization, request capture, validated node outcomes, sequential workflows, persisted pause/resume, bounded repair/crash detection, Codex/Cursor adapters, and local package installation/upgrades. Hosted Windows, macOS and Linux checks exercise the scenario and package install/upgrade suites. The public package identity is @rogeriohsjr/nodulus; release and registry validation status is recorded in folder 09. The generated project has no configured provider. Adapter tests use real local fixture executables; Codex, OpenCode/Ollama, and Cursor have separate Windows live proof, while macOS/Linux live-provider compatibility remains pending.

The current feature branch adds bounded feedback routing and read-only inspection/export/replay. FB-010/030/040/045/060 have independent local review; FB-050 is a green local candidate awaiting review and the final repository check. This branch status does not change the currently published npm package.

Start with the implementation sequence. Each numbered folder contains scenarios, implementation guidance, checkboxes, and an evidence record.

Repository skills: $nodulus-scenario-tdd and $nodulus-delivery-validation.

For development, use Node.js 24, run npm ci, then npm run check to run lint, typecheck, scenarios and package checks.

For a local bounded feedback-routing walkthrough, see the normalization and review example. It uses a controlled child-process fixture and the exported API without calling a live provider.

Contribute and license

Issues and pull requests are welcome. See the contribution guide for the development workflow and test expectations.

Copyright 2026 Rogeriohsjr and Nodulus contributors. Licensed under Apache-2.0, with attribution in NOTICE. You may use, copy, modify and redistribute this project under those terms.

Develop with Nodulus

The development workflow example connects an OpenCode/Qwen test author, Luna test reviewer, OpenCode/Qwen implementer and GPT-5.6 Sol final reviewer. An actual npm run check validator gates completion. A separate verification workflow checks existing work, and escalation is optional. See the example for isolated-worktree setup, required CLI versions and live-validation limitations.