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

@elyracode/workflows

v0.9.9

Published

Code-orchestrated workflows for Elyra -- define multi-step pipelines where code handles control flow and LLMs handle judgment

Readme

@elyracode/workflows

Code-orchestrated workflows for Elyra. Define multi-step pipelines where code handles the control flow and the LLM handles judgment — no token tax from LLM-based orchestration.

Why

Traditional agent orchestration uses one LLM to plan, spawn sub-agents, collect results, and decide next steps. Every sub-agent result re-enters the orchestrator's context window, paying a "token tax" that degrades quality as the window fills.

Workflows flip this: code orchestrates, the LLM only judges. Each step is focused, deterministic, and reproducible.

Install

elyra install npm:@elyracode/workflows

Usage

Create workflow files in .elyra/workflows/:

{
  "name": "deploy",
  "description": "Build, test, review, deploy",
  "steps": [
    { "name": "test", "run": "npm test" },
    { "name": "review", "prompt": "Review test results:\n{{steps.test.output}}" },
    { "name": "deploy", "run": "npm run deploy", "if": "{{steps.test.code}} == 0" }
  ]
}

Run with /workflow deploy or ask the agent to run it.

Step Types

  • prompt — Send a focused prompt to the LLM
  • run — Execute a shell command
  • if — Conditional execution based on previous step results
  • parallel — Run multiple steps concurrently

Template Variables

Reference previous step outputs with {{steps.<name>.output}}, {{steps.<name>.code}}, or {{steps.<name>.stderr}}.