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

scriptory

v0.1.2

Published

Internal documentation platform with Notion-like editor, team collaboration, and version control

Downloads

345

Readme

scriptory

A lightweight, local-first internal documentation tool with a Markdown editor. Think Notion, but it runs entirely on your machine and stores everything as plain .mdx files in your repo.

Install

npm install -g scriptory

Usage

# Start the server (opens browser automatically)
scriptory

# On a custom port
scriptory --port 8080

# Initialise a new project in the current directory
scriptory init

# Check for updates
scriptory update

# Configure editor deeplinks (e.g. open files in VS Code)
scriptory set DEEPLINK_PREFIX vscode://file
scriptory get DEEPLINK_PREFIX

How it works

Running scriptory in a project directory starts an Express server at http://localhost:6767 and opens the UI in your browser. Documentation is stored inside a scriptory/ folder in the current directory — each page is a sub-folder containing:

scriptory/
  getting-started/
    config.json      ← title + icon
    content.mdx      ← Markdown content
  architecture/
    config.json
    content.mdx

Because everything is plain files, docs live alongside your code and are committed to version control.

Features

  • Markdown + MDX — GFM tables, fenced code blocks with syntax highlighting
  • Insert code files — Browse your project and embed files as code blocks in one click
  • Deep links — Configure a prefix (e.g. vscode://file) to make file paths in docs clickable
  • Keyboard shortcuts⌘S to save, ⌘P to toggle preview, ⌘N for a new doc
  • Zero cloud — everything stays local; no accounts, no sync, no tracking

Development

git clone https://github.com/anandpilania/scriptory
cd scriptory
npm install

# Run backend + frontend dev servers concurrently
npm run dev

The frontend (Vite + React) runs on :3000 and proxies /api to the backend on :6767.

License

MIT