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

openapi-to-postman-complete

v1.3.0

Published

Complete OpenAPI to Postman converter with filtering, descriptions, examples, variables, and auto-generated tests

Readme

OpenAPI to Postman Complete

Complete OpenAPI to Postman converter. One command. Production-ready collections.

npm version License: MIT

Why not just use openapi-to-postmanv2?

The official converter gives you valid Postman collections. We give you usable Postman collections.

Built on top of Postman's official openapi-to-postmanv2 converter, adding:

  • Endpoint filtering - Keep only what you need
  • Resource organization - Nested folders by REST hierarchy
  • Rich descriptions - Human-friendly documentation
  • Real examples - Actual request/response data
  • Path variables - Automatic environment variable mapping
  • Auto-generated tests - Validation out of the box
  • ID preservation - Maintain bookmarks across regenerations

Installation

npm install -g openapi-to-postman-complete

Quick Start

openapi-to-postman-complete api.yaml config.yaml -o collection.json

That's it. OpenAPI → production-ready Postman collection in one command.

No need to run openapi-to-postmanv2 separately - we handle that internally.

Configuration

Create a config.yaml with what you need:

Minimal

variables:
  environment:
    baseUrl: https://api.example.com

tests:
  auto: true

With Filtering

filter:
  include:
    GET /users: true
    POST /users: true

variables:
  environment:
    baseUrl: https://api.example.com

tests:
  auto: true

Full Example

filter:
  include:
    GET /pets: true
    POST /pets: true
    GET /pets/:id: true

organize:
  enabled: true
  strategy: resources
  nestingLevel: 2

descriptions:
  collection:
    Pet Store API:
      name: Pet Store - Developer Collection

  requests:
    List pets: Get all pets from the store

examples:
  responses:
    List pets:
      code: 200
      body:
        - id: '1'
          name: Buddy

variables:
  environment:
    baseUrl: https://api.petstore.com
    petId: '1'

pathVariables:
  enabled: true
  mapping:
    id:
      reference: '{{petId}}'
      description: Pet ID

tests:
  auto: true

See examples for more.

Programmatic Usage

import { enrichCollection } from '@postman-enricher/core';

const collection = JSON.parse(readFileSync('collection.json', 'utf8'));

const enriched = enrichCollection(
  collection,
  {
    organize: { enabled: true, strategy: 'resources' },
    pathVariables: {
      enabled: true,
      mapping: { id: { reference: '{{petId}}' } },
    },
    tests: { auto: true },
  },
  './existing-collection.json' // Optional: preserves IDs
);

Or load config from YAML:

const enriched = enrichCollection(
  collection,
  './config.yaml',
  './existing-collection.json'
);

License

MIT