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

@findyourmodel/cran

v0.1.7

Published

Cran CLI — log in once, install the MCP, and use Cran in any repo (link optional, for routing live traffic).

Readme

@findyourmodel/cran

Cran CLI — device login, project linking, proxy smoke tests, and IDE MCP install.

Full guide: docs/cli.md and https://trycran.in/docs/cli

Install

# Do NOT use: npm i -g cran  (wrong package on npm)

npm i -g @findyourmodel/cran

# From monorepo:
npm run build:cli && npm i -g ./packages/cli

Quick start

Connect once, then "use Cran" works everywhere on your account's default project:

cran login                # browser sign-in, once per machine
cran mcp install cursor   # or claude / windsurf / codex

Then tell your agent: Use Cran for model selection. No per-repo cran link is needed — switch projects from the agent with the fym_use_project MCP tool.

cran link is optional — run it only to route your app's live traffic through the Cran proxy (it writes a connection key to .env). Then cran dev smoke-tests model: auto.

Which project is this repo?

  • Per repo: .cran/config.toml (project_id, project_slug)
  • Per machine: ~/.cran/session.json (from cran login)
cran whoami
cran status
cran projects list
cran link --project-id proj_…

Commands

| Command | Purpose | |---------|---------| | cran login | Browser device auth → ~/.cran/session.json | | cran logout | Remove session | | cran whoami | Session + linked project (cwd) | | cran projects list | All account projects | | cran projects ensure | Create/find the dashboard product for this repo | | cran link | (optional) mint a connection key + write .env to route live traffic | | cran init | .env.example, gitignore, config template | | cran status | Link + Connected check | | cran dev | Smoke-test model: auto via proxy | | cran open | Dashboard for linked project | | cran mcp install <ide> | Cursor / Claude / Windsurf / Codex MCP | | cran mcp run | Run Cran MCP with session env |

Tokens

  • User CLI token (cran login) — CLI and MCP only
  • Connection token (cran link → OPENAI_API_KEY) — your app and production

Never commit .env.