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

@gyeonghokim/openapi-converter

v1.1.0

Published

Convert API collection files (Postman, Apidog, Bruno) to OpenAPI v3 format

Downloads

185

Readme

openapi-converter

Convert API collection files (Postman, Apidog, Bruno) to OpenAPI v3 format.

Features

  • Convert Postman Collections to OpenAPI v3
  • Convert Apidog Collections to OpenAPI v3
  • Convert Bruno Collections to OpenAPI v3

Installation

npm install -g @gyeonghokim/openapi-converter

Or use locally:

npm install --save-dev @gyeonghokim/openapi-converter

Usage

openapi-converter <input-file> [options]
# or just
oac <input-file> [options]

Options:
  -o, --output <path>       Output file path (default: openapi.json, only supports json and yaml formats)
  -p, --provider <provider> Provider to use (default: postman, only supports postman, apidog, bruno)
  -h, --help                Show help message

Examples

# Convert Postman collection
openapi-converter collection.json -o api-spec.json

# Convert Apidog collection
openapi-converter apidog-export.json

# Convert Bruno collection
openapi-converter bruno-collection.json -o openapi.yaml

Development

Setup

# Clone the repository
git clone <repository-url>
cd openapi-converter

# Install dependencies
npm install

Available Scripts

# Build the project
npm run build

# Run tests
npm test

# Run tests in watch mode
npm run test:watch

# Run tests with UI
npm run test:ui

# Run linter
npm run lint

# Format code
npm run format

# Check and fix formatting and linting
npm run check

# Development mode (watch)
npm run dev

Project Structure

openapi-converter/
├── src/
│   ├── cli.ts           # CLI entry point
│   └── index.ts         # Main conversion logic
├── test/
│   └── index.test.ts    # Tests
├── dist/                # Build output (generated)
├── biome.json           # Biome configuration
├── tsconfig.json        # TypeScript configuration
├── commitlint.config.js # Commitlint configuration
└── package.json         # Project configuration

Git Hooks

This project uses Husky for Git hooks:

  • pre-commit: Runs lint-staged to check and format staged files
  • commit-msg: Validates commit messages against conventional commit format

Commit Message Format

This project follows Conventional Commits:

<type>(<scope>): <subject>

<body>

<footer>

Types:

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation changes
  • style: Code style changes (formatting, etc.)
  • refactor: Code refactoring
  • perf: Performance improvements
  • test: Adding or updating tests
  • build: Build system changes
  • ci: CI configuration changes
  • chore: Other changes

License

MIT