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

service-status-cli

v0.0.14

Published

A command line interface to query the status page of key service providers and provide a uniform response.

Downloads

17

Readme

A command line interface to query the status page of key service providers and provide a uniform response.

Service data

There is a list of services that comes from this repository. Currently this is a very limited number of services, but we'd love more. Please add your service into that repo and it will get updated.

Installation

npm i service-status-cli

Usage

This library installs itself as the status command.

status [service] returns the status for that service.

For example when something is Operational:

➜  $ status github
✔ GitHub 👉 operational

Partial Outage or in Maintenance:

➜  $ status slack
⚠ slack 👉 partial outage
"Slowness searching in Slack" see: https://status.slack.com/

Options

  • --list returns the services available.
  • --web opens the web page for the service in your browser.
  • --all returns the status for all services.
  • -v or --verbose get verbose logging, including URL to the endpoint used.
  • -q suppress all output, except errors. Exit codes are returned see below 👇

Exit codes

The CLI will exit with certain exit codes depending upon the result:

| Exit code | Description | | --------- | ------------------------------------------------------------------- | | 0 | The command completed succesfully, or the service is Operational. | | 1 | The command had an error unrelated to the service status. | | 2 | The service has a Partial Outage. | | 3 | The service has a Major Outage | | 4 | The service is in Maintenance. |

Service status

This library is taking multiple different services and trying to apply a standard to them. This is inherently lossy and imperfect. However there's some common themes in the statuses that systems use and we try to use [^1]

| Status | Description | | ---------------- | ----------------------------------------------------------------------- | | Operational | No incidents reported. | | Partial Outage | A partial or minor incident declared in some components by the service. | | Major Outage | A major incident declared by the service. | | Maintenance | Service is in a maintenance window. |

[^1]: Expecting this will evolve rapidly if services get added.

Development

Pull requests and issues are welcome.

Note: Testing is currently pinned to node 19.4.0 as per the Action, because that's the version that msw seems to work on. To test:

npm test

See vitest for more information about the test framework.