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

@vortex-api/pile

v0.1.6

Published

Pile SDK + CLI + capture + widget — one package for the whole Pile surface.

Downloads

1,150

Readme

@vortex-api/pile

Pile — the agent-native issue tracker and support desk. The support ticket and the engineering issue are the same object; coding agents are first-class users that record bugs, read capture artifacts, and open fix PRs.

One package ships the whole surface:

| Import / command | What | | ---------------------------------- | ---------------------------------------------------------------------------- | | @vortex-api/pile | TypeScript SDK (createPileClient, typed OpenAPI client) | | @vortex-api/pile/capture | Browser capture SDK — console, network, errors, rrweb replay, debugger state | | @vortex-api/pile/chat.js | Embeddable support widget (IIFE) | | @vortex-api/pile/capture.iife.js | One-tag capture script | | pile | CLI — issues, tickets, agent sessions, capture |

Quickstart

npm i @vortex-api/pile
pile init        # sign up → workspace → API key, one command

Or drive the API directly:

curl -X POST https://pile.nyc/api/auth/sign-up/email \
  -H 'Content-Type: application/json' \
  -d '{"email":"[email protected]","password":"…","name":"You"}'

curl -X POST https://pile.nyc/workspaces/onboard \
  -H 'Cookie: <session>' -H 'Content-Type: application/json' \
  -d '{"name":"Acme","slug":"acme","key":"ACM"}'
# → { workspace, team, token }

Embed capture

<script
  src="https://pile.nyc/capture.js"
  data-pile-key="pil_…"
  data-pile-replay="true"
></script>

or programmatically:

import { initCapture } from "@vortex-api/pile/capture";
const capture = initCapture({ publicKey: "pil_…" });

Support widget

<script src="https://pile.nyc/chat.js" data-pile-widget="wgt_…"></script>

For agents

  • GET /llms.txt — machine-readable index of surfaces and docs
  • GET /llms-full.txt — the full docs corpus
  • POST /mcp — MCP server exposing issue/ticket/workspace tools
  • GET /openapi.json — the full API contract

Apache-2.0 · https://pile.nyc