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

@vottuscode/response-spec

v1.0.1

Published

This spec is for made for JSON responses.

Readme

Vottus' Response Specification

This spec is for made for JSON responses.

General

  • API always returns a Content-Type: application/json header

Status Code

You always send a HTTP code of 200, but there are 2 exceptions:

  • Internal Server Error (error kind: internal) - HTTP code 500
  • Validation Error (error kind: validation) - HTTP code 400

Successful Response

Successful response passes a success property that is of value true, like so:

{
  "success": true
}

Additionally, when passing data in the response, you may create a data object inside of which you create appropriate property, for example:

{
  "success": true,
  "data": {
    "user": {
    }
  }
}

You may pass multiple properties inside of the data objects. You may also pass a string, boolean, or a different kind of primitive as a value of data properties:

{
  "success": true,
  "data": {
    "user": {
    },
    "loginValidUntil": "2021-01-04T07:19:18.080Z"
  }
}

Failed/Error Response

Response that fails whether because of user input or because of internal error passes a success property that is of value false and an error object with properties "kind" and "message":

{
  "success": true,
  "error": {
    "kind": "user_input",
    "message": "Invalid token"
  }
}

Kind represents the kind of error that occurred or why the error occurred in the first place. Commonly, following kinds are used:

  • user_input
    • Meaning that error occurred because of some sort of user input, for example missing/invalid request body/headers
  • unauthorized
    • Meaning that the user is not authorized for the endpoint. Eg. not logged in.
    • When the user is however authenticated in some form but is not allowed to perform certain actions, forbidden is used instead!
  • forbidden
    • Meaning that user is authenticated but unauthorized to perform certain action.
  • internal
    • Internal Server Error. For this kind an HTTP code 500 is sent.
  • validation
    • Validation Error. For this kind an HTTP code 400 is sent.

Message is a localized message further describes the error that occurred.