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

@docnineai/cli

v1.0.0

Published

AI-powered documentation, security auditing, and codebase Q&A in your terminal

Readme

Docnine CLI

An AI-powered documentation tool for developers and Project Manager in your terminal.

npm install -g docnine

Commands

Setup

docnine login
docnine login --token <token>
docnine logout
docnine whoami
docnine init

Core

docnine generate
docnine generate --watch
docnine generate --format md

docnine ask "how does auth work?"
docnine ask --file src/auth.js
docnine ask --interactive

docnine audit
docnine audit --fail-on CRITICAL
docnine audit --fail-on HIGH
docnine audit --format json
docnine audit --format sarif

docnine diff
docnine diff --since v1.2.0
docnine diff --since HEAD~10
docnine diff --format json

docnine export --format openapi
docnine export --format postman
docnine export --format markdown
docnine export --format pdf
docnine export --out ./exports

CI/CD

docnine ci
docnine ci --fail-on HIGH
docnine ci --comment-pr
docnine ci --format json

logged in + linked project. Files are sent to Docnine server for full pipeline processing.

File Collection Rules

  • Recursively scans current directory
  • Respects .gitignore and .docnineignore
  • Skips: node_modules, .git, dist, build, coverage, *.min.js
  • Collects: .js .ts .tsx .jsx .py .go .rs .java .prisma .graphql .sql

Config Files

Auth config (~/.docnine/config.json, chmod 600):

{
  "token": "...",
  "user": {
    "id": "...",
    "email": "[email protected]",
    "name": "Your Name",
    "plan": "pro"
  }
}

Project config (.docnine.json):

{
  "projectId": "...",
  "outputDir": "./docs",
  "offline": false
}

Run snapshot (.docnine/last-run.json): used by diff, export, and ci.

Environment Variables

  • DOCNINE_API_URL (default: https://api.docnineai.com)
  • DOCNINE_URL (default: https://docnineai.com)
  • DOCNINE_API_TOKEN (optional token fallback)

The CLI auto-loads .env from the current working directory (for example DOCNINE_API_URL=http://localhost:3000).

Exit Codes

  • 0 on success
  • 1 on command error or fail threshold exceeded