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

@xec-sh/ops

v0.13.2

Published

DevOps operations library — deploy, health checks, pipelines, discovery, workflows

Readme

@xec-sh/ops

Workflow and operations tooling built on Xec Core: pipelines, deployment strategies, configuration, secrets, target discovery, and resumable package releases.

npm install @xec-sh/ops

Requires Node.js 20 or later. Operations reuse Core execution and cancellation, Loader scripting, and Kit presentation.

Orchestrate a workspace

import { Pipeline } from '@xec-sh/ops/pipeline';

const result = await Pipeline.create('workspace-checks')
  .step('workspace', {
    run: {
      command: 'pnpm',
      args: ['exec', 'turbo', 'run', 'build', 'test', 'typecheck'],
      shell: false,
    },
    timeout: 30 * 60_000,
  })
  .run();

if (!result.success) {
  throw new Error(result.steps.filter(step => !step.success)
    .map(step => `${step.name}: ${step.error ?? step.exitCode}`).join('\n'));
}

The workspace runner owns package dependencies and build caching. Xec owns preparation, execution, progress, and cleanup around it. An infrastructure controller owns deployed state and recovery. Keep each responsibility in one place.

Capabilities

| API | Responsibility | | --- | --- | | Pipeline / Workflow | Dependencies, conditions, parallel work, and task results | | Deployer | Rolling, blue-green, canary, and all-at-once strategies with project hooks | | HealthChecker / Discovery | Health observations and target discovery | | ConfigurationManager / TargetResolver | Project configuration, profiles, and named targets | | SecretManager | Secret storage with pluggable providers | | TaskManager / TaskExecutor | Configured task execution | | OutputFormatter | Shared CLI presentation through Kit | | @xec-sh/ops/release | Immutable archives, publication journals, registry confirmation, and resume |

Pipeline matrix values expand environment variables; they do not install runtimes. The reserved pipeline cache field does not implement artifact caching.

Releases

Release preparation builds a clean checkout and seals package archives. Resume verifies and publishes those archives without rebuilding or rerunning the test suite. Accepted or reserved npm uploads are reconciled from the saved journal before any further upload.

Use the release API and CLI workflow for preparation, authentication, registry visibility, and recovery. An explicit verified ancestor can define the release-notes range; tags alone are not publication evidence.

Cancellation

The CLI passes a Core cancellation scope through commands and cooperative callbacks. Awaited actions release their owned resources before exit, within a bounded grace period. Cleanup commands use withoutCancellation with their own budget; unrelated work is not cancelled.

Documentation · Pipelines · Release workflow · MIT license