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 🙏

© 2025 – Pkg Stats / Ryan Hefner

scriptor-ai

v1.0.3

Published

AI‑powered CLI and GitHub Action for generating code documentation and examples using OpenAI LLMs.

Downloads

15

Readme

Scriptor

npm version
License
Build Status

Scriptor is your AI‑driven “Docs CI/CD” for codebases: continuously generate, validate, and enrich Markdown docs, code examples, and diagram, directly in your CLI, IDE, or web portal.

“Make documentation as effortless, reliable and dynamic as writing code.”


Table of Contents


Features

  • Continuous Documentation: GitHub Action or CLI plugin auto‑comments PRs with fresh docs.
  • Multi‑Prompt Agent: function-summary, module-overview, changelog templates, hot‑reloadable via PromptManager.
  • Streaming & Large Context: Leverage GPT‑4.1’s 1 M token window and streaming API for real‑time feedback.
  • IDE Integrations: VS Code & JetBrains plugins for inline docs.
  • Web Portal: (“Scriptor Hub”) TBD, for cross‑functional stakeholders.

Getting Started

Prerequisites

  • Node.js ≥ 18 LTS
  • npm or yarn
  • OpenAI API key (for local dev via .env)

Installation

git clone https://github.com/xcoder-nz/scriptor.git
cd scriptor
npm install

Create a .env file at project root:

echo "OPENAI_API_KEY=sk-…" > .env

Usage

CLI

# Summarize a function
npx ts-node cli/generate.ts generate function-summary --file examples/foo.py

# Module overview
npx ts-node cli/generate.ts generate module-overview --file examples/analytics.py

# Changelog
npx ts-node cli/generate.ts generate changelog --file examples/change.diff

GitHub Action

Add to .github/workflows/docs.yml:

on: [pull_request]
jobs:
  docs:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: xcoder-nz/scriptor-action@v1
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}

Prompt Templates

Located in cli/prompts/:

  • function-summary.txt: Summarizes single functions.
  • module-overview.txt: Lists classes/methods in tables.
  • changelog.txt: Generates Markdown changelogs from diffs.

Edit these .txt files on‑the‑fly—no recompilation required.


Testing

npm test        # runs Jest unit & integration tests
npm run lint    # ESLint checks
npm run type    # TypeScript compiler checks

CI is configured in .github/workflows/ci.yml to run tests on push and PR citeturn0search4.


Roadmap

See ROADMAP.md for upcoming milestones: v1.0 IDE plugins, v1.1 Web Portal, Enterprise features.


Contributing

  1. Fork the repo
  2. Create a feature branch (git checkout -b feat/name)
  3. Run tests (npm test)
  4. Open a PR and reference this issue

Please follow the Standard Readme Spec.


License

MIT © XCoder NZ