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

@spotify-confidence/quickstart

v1.5.0

Published

Get started with Confidence in minutes.

Readme

Highlights

  • Zero-to-flags in one command — run npx @spotify-confidence/quickstart and the interactive wizard handles the rest
  • Auto-detects your stack — React, Next.js, Node, Python, Swift, Kotlin, Java, and Go; installs the matching Confidence SDK
  • Connects your AI assistant — configures MCP servers and IDE plugins for Claude Code, Cursor, or Codex so your agent can manage flags inline
  • Guided onboarding — generates project context files that teach your AI assistant how your Confidence setup works
  • Migrating from another platform? Pair with Confidence AI Plugins for one-command migrations from PostHog, Eppo, Statsig, or Optimizely

Quick Start

npx @spotify-confidence/quickstart

Requires Node.js 24+.

Confidence AI Plugins

Prefer to manage the integration yourself? confidence-ai-plugins provides standalone plugins that give AI agents the ability to manage feature flags, work with documentation, run migrations, and more — without the guided wizard flow.

Documentation

Community & Support

Found a bug or have a feature request? Open an issue.


Usage

confidence-quickstart [command] [options]

Commands

| Command | Description | | ----------- | ----------------------------------- | | (default) | Launch the interactive setup wizard | | start | Alias for the default command | | help | Show the help message |

Options

| Option | Description | | ---------------- | ------------------------------------------------- | | --dir <path> | Project directory to run the wizard in | | --dry-run | Run without making real API calls | | --debug | Enable debug output and preserve terminal history | | --no-telemetry | Disable anonymous usage telemetry |

Security Note

During the project onboarding step, the wizard spawns your chosen AI agent to integrate the Confidence SDK into your project. You will be prompted to confirm before this step begins. Each agent runs with different permissions:

  • Claude Code — Spawned in non-interactive (--print) mode using its standard permission model. It can read files and execute tools within your project directory as allowed by your existing Claude Code settings. No elevated trust flags are applied.
  • Cursor — Spawned in agent mode with --trust, which grants full read/write access to files in your project directory and allows it to run shell commands (e.g. npm install) without individual approval prompts. MCP server connections are also auto-approved (--approve-mcps).
  • Codex — Spawned in exec mode with --sandbox danger-full-access, which grants unrestricted filesystem and network access. It can read and write any file, run shell commands, and make network requests without sandboxing restrictions. Full access is required because the onboarding agent needs to install npm packages, modify project configuration files, and download SDK dependencies — operations that Codex's default sandbox would block.

All agents are scoped to your project directory and run with a timeout. The wizard installs a Confidence skill/plugin and connects MCP servers before spawning the agent, so configuration files may already be written to your project at that point.

Telemetry

The wizard collects anonymous usage data (e.g. which steps you complete) to help improve the experience. No personal or project data is collected.

To opt out:

npx @spotify-confidence/quickstart --no-telemetry

Or set the environment variable:

CONFIDENCE_TELEMETRY=false npx @spotify-confidence/quickstart

Telemetry is automatically disabled in CI environments and during development.

Development

pnpm install
pnpm try          # Run the wizard locally via tsx
pnpm test         # Run vitest
pnpm lint         # ESLint + Prettier check
pnpm typecheck    # TypeScript type checking
pnpm qa           # Run all checks (typecheck + lint + test)
pnpm build        # Build for distribution

Troubleshooting

E2E tests fail to install or build

E2E tests use node-pty to drive the TUI in a real terminal. This native module requires platform-specific build tools. If pnpm install fails on node-pty, install the prerequisites listed at https://github.com/microsoft/node-pty#dependencies.

E2E tests fail with posix_spawnp failed

The stable node-pty release (v1.1.0) doesn't ship prebuilt binaries for Node.js v26+. The project uses [email protected] which includes updated Node-API bindings for newer Node versions. If you hit this error on a newer Node version, ensure the beta is installed. On CI with Node 24, the stable release works fine.

License

Apache License 2.0