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

pm2oa

v1.0.0

Published

postman2openapi CLI

Readme

pm2oa

A lightweight CLI tool to convert Postman collections to OpenAPI specifications using postman2openapi.

This package targets Node.js 18+ because it relies on the built-in fetch API (no polyfill included). Ensure fetch is available when running in custom environments.

Installation

npx pm2oa

Usage

Convert from URL

npx pm2oa https://some.postman.spec/

Convert from URL to specific output file

npx pm2oa https://some.postman.spec/ -o output.yml

Convert from local JSON file

npx pm2oa postman-spec.json

Force YAML output regardless of extension

npx pm2oa postman-spec.json --format yaml

Convert from stdin

cat postman-spec.json | npx pm2oa

or

npx pm2oa < postman-spec.json

Output Formats

  • JSON (default): Outputs OpenAPI specification as JSON
  • YAML: Use --format yaml or an output path ending with .yml or .yaml

Options

  • [input] - Input file path or URL to Postman collection (optional; errors when stdin is empty)
  • -o, --output <file> - Output file path (defaults to stdout)
  • -f, --format <format> - Output format (json or yaml)
  • -h, --help - Display help information
  • -V, --version - Display version number

Development

  • npm run lint – Syntax check index.js
  • npm test – Smoke test JSON and YAML outputs against a fixture

Publishing

  • Releases run the .github/workflows/publish.yml workflow (triggered on release publish and manually via workflow_dispatch).
  • The workflow executes npm ci, then npm run lint / npm test, and finally npm publish --access public --provenance with the NPM_TOKEN repository secret supplied as NODE_AUTH_TOKEN.
  • Keep versions bumped before invoking the workflow and verify tests/lint pass locally (npm run lint, npm test, optionally npm pack) so the pipeline can succeed without intervention.