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

k25-swagger-fetch

v1.1.0

Published

Download Swagger JSON from password-protected endpoints

Readme

k25-swagger-fetch

Download Swagger JSON from password-protected endpoints.

Installation

bun add -d k25-swagger-fetch

Usage

CLI

# Uses SWAGGER_URL, SWAGGER_USER, SWAGGER_PASSWORD from .env
swagger-fetch

# With explicit parameters
swagger-fetch --url https://api.example.at/swagger/v1/swagger.json --output ./scripts/swagger.json

# With all flags
swagger-fetch --url <url> --user swagger --password <pw> --output ./scripts/swagger.json

Environment Variables

Create a .env file:

SWAGGER_URL=https://your-project.k25-dev.at/api/swagger/v1/swagger.json
SWAGGER_USER=swagger
SWAGGER_PASSWORD=your-password
SWAGGER_OUTPUT=./scripts/swagger.json

Config File

Create swagger-fetch.config.ts (auto-detected):

import { defineConfig } from "k25-swagger-fetch";

export default defineConfig({
  url: "https://your-project.k25-dev.at/api/swagger/v1/swagger.json",
  output: "./scripts/swagger.json",
  // username/password should stay in .env
});

Programmatic API

import { fetchSwagger } from "k25-swagger-fetch";

await fetchSwagger({
  url: "https://api.example.at/swagger/v1/swagger.json",
  username: "swagger",
  password: "secret",
  output: "./scripts/swagger.json",
});

Resolution Order

CLI flags > environment variables > config file > defaults

| Option | CLI Flag | Env Var | Default | | -------- | ------------ | ------------------ | ------------------------ | | url | --url | SWAGGER_URL | — | | username | --user | SWAGGER_USER | swagger | | password | --password | SWAGGER_PASSWORD | "" | | output | --output | SWAGGER_OUTPUT | ./scripts/swagger.json |

Integration Example

{
  "scripts": {
    "download-swagger": "swagger-fetch",
    "generate-client": "openapi-ts",
    "openapi-ts": "bun run download-swagger && bun run generate-client",
    "dev": "bun run openapi-ts && vite"
  }
}