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 🙏

© 2024 – Pkg Stats / Ryan Hefner

openapi-type-finder

v1.0.12

Published

Finds list of objects of given type from OpenAPI document.

Downloads

15

Readme

Description

CLI Application that lists objects with given type from OpenAPI document.

Note - Even though all types have been seperately tested, there is a chance of errors. If such a thing happens please contact the authors.

Installation

npm i -g openapi-type-finder

Target

    openapi-type-finder -u <url> -t <type> (optional) --no-resolve

Use --no-resolve if you want the references in the document to not be resolved, though it may lead to inacurrate behaviour.

Test

Input url: https://api.apis.guru/v2/specs/xkcd.com/1.0.0/openapi.yaml

Input type: responses

Output:

{
    "content": {
        "*/*": {
            "schema": {
                "$ref": "#/components/schemas/comic"
            }
        }
    },
    "description": "OK"
}

Types Done:

A checklist for which types have been implemented.

  • [x] schemas
  • [x] responses
  • [x] parameters
  • [x] examples
  • [x] requestBodies
  • [x] headers
  • [x] securitySchemes
  • [x] links
  • [x] callbacks
  • [x] pathItems

Schemas (4)

  • parameterObject.schema -> Schema Object
  • requestBody.content[x].schema -> Schema Object
  • response[x].content[y].schema -> Schema Object
  • headerObject[x].schema -> Schema Object

Responses (1)

  • pathItemObject[x].responses.y -> {Status Code/ "default" : Response Object | Reference Object}

Parameters (2)

  • pathItem[x].parameters[y] -> Parameter Object | Reference Object
  • pathItem[x][y].parameters[z] - > Parameter Object | Reference Object

Examples (4)

  • requestBody.content[x].examples.y -> {name: Example Object}
  • response[x].content[y].examples.z -> {name: Example Object}
  • parameterObject.examples.x -> {name: Example Object}
  • headerObject[x].examples.y -> {name: Example Object}

Request Bodies (1)

  • pathItemObject[x].requestBody -> Request Body Object | Reference Object

Headers (2)

  • requestBody.content[x].encoding[y].headers.z ->{name: Header Object | Reference Object}
  • responseObject[x].headers.y -> {name: Header Object | Reference Object }

Security Schemes (1)

  • document.components.securitySchemes.x -> { name : Security Scheme Object | Reference Object}

Each name MUST correspond to a security scheme which is declared in the Security Schemes under the Components Object. Security Schemes are not defined anywhere else.

Links (1)

  • response[x][y].links.z -> {name: Link Object | Reference Object}

callbacks (1)

  • pathItem[x][y].callbacks.z -> {name: Callback Object | Reference Object}

pathItems (3)

  • document.paths.x -> {path:Path Item Object | Reference Object}
  • callbacks[x].y -> {path:Path Item Object | Reference Object}
  • document.webhooks.x -> {path:Path Item Object | Reference Object}