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

@generata/core

v1.2.0

Published

Composable multi-agent pipelines on top of the Claude Code CLI.

Readme

@generata/core

Composable multi-agent pipelines on top of the Claude Code CLI.

npx @generata/core init @generata/starter ~/Projects/hello-generata
# or: pnpm dlx @generata/core init @generata/starter ~/Projects/hello-generata

Public API

import { defineAgent, defineWorkflow, defineConfig } from "@generata/core";

That's all you need to author agents, workflows, and a project config.

For workflows that need git-worktree isolation, also import worktree:

import { defineWorkflow, worktree } from "@generata/core";

defineWorkflow({
  isolation: worktree({ sharedPaths: ["state.md"] }),
  // ...
});

CLI

| Command | Purpose | | :-------------------------------- | :---------------------------------------------------------- | | generata <name> | Run a workflow (shorthand for workflow <name>) | | generata init <template> [dest] | Scaffold a new project from a template | | generata add <template> | Merge a template into the current project | | generata agent <name> | Run a single agent | | generata workflow <name> | Run a workflow (alias: run) | | generata validate [--all] | Static-check workflow definitions | | generata metrics [today\|week] | Show metrics summary | | generata skills sync | Regenerate .claude/commands/ from workflows | | generata worktree prune | Remove orphan generata/wt-* worktrees and branches | | generata help [topic] | Show help (topics: agents, workflows, env, templates, bins) |

Workflow flags: --worktree forces git-worktree isolation for the run; --local forces it off (mutually exclusive).

Template specifiers

generata init accepts:

  • @generata/<alias> - resolves via the built-in catalog
  • <owner>/<repo> - resolves to https://github.com/<owner>/<repo>.git
  • git@... / https://....git - any git URL
  • ./path / /abs/path - a local directory containing generata.template.json

Init flags

  • --yes - non-interactive; required env values default to manifest examples
  • --skip-preflight - skip required-bin checks
  • --skip-install - skip the package-manager install step (useful offline)

Add flags

  • --force - overwrite conflicting files
  • --dry-run - print what would be written
  • --into <subdir> - merge into a subdirectory rather than the project root

Development (in the ApexGen monorepo)

pnpm install                            # links the workspace
pnpm --filter @generata/core build      # rebuild dist/ after engine changes
node --test --import tsx generata/src/**/*.test.ts

The exports map uses a development condition that points at src/ so workspace dev runs through the TypeScript source via tsx; published consumers see the compiled dist/ output.

See CHANGELOG.md for release notes.