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

@callstack/apex

v0.2.2

Published

Detects the AI coding assistants installed on your machine and configures them to use Callstack Apex.

Downloads

439

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

souhesouhethymikeethymikeegrabbougrabbousatya164satya164mdjastrzebskimdjastrzebskijbindajbindaartus9033artus9033rafikitikirafikitikiadmin-callstackadmin-callstackhur.ali.ckhur.ali.ckjbromajbromamateusz1913mateusz1913robikrobikdannyhwdannyhwxeonbloomfieldxeonbloomfieldpiotrskipiotrskitrozeetrozeecamobapcamobap

Keywords

callstackapexai

Readme

Apex CLI

Configures the AI coding assistants installed on your machine to use Callstack Apex.

Install

npx @callstack/apex init

What init does

It detects which of these are installed and writes (or updates) their config to point at Apex, backing up any existing file first (<file>.bak-<timestamp>):

| Assistant | Config written | | --- | --- | | Claude Code | ~/.claude/settings.json | | Codex | ~/.codex/config.toml, ~/.codex/callstack_ai.config.toml | | OpenCode | ~/.config/opencode/opencode.json (v1 or v2 format, auto-detected), ~/.local/share/opencode/auth.json (if absent, v1 only) | | pi | ~/.pi/agent/models.json | | Cursor | manual steps (GUI-only, printed to the terminal) | | VS Code + GitHub Copilot | manual steps (GUI-only, printed to the terminal) | | Vercel AI SDK / Eve | .env in the current project, if it depends on ai/eve |

You'll be prompted for your Apex API key (input hidden), or pass it directly:

npx @callstack/apex init --api-key sk-XXX
# or
APEX_API_KEY=sk-XXX npx @callstack/apex init --yes

Other flags: --dry-run (show changes without writing), --only <ids> / --skip <ids> (comma-separated, see apex list for ids).

Commands

apex init      # detect + configure
apex list      # show which assistants are detected, without changing anything

Security

Your Apex API key is written locally to config files under your home directory (and, for JS projects, to a local .env). Never commit these files or share the key. Rotate it if you suspect it leaked.