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

github-ci-status

v1.0.0

Published

Check the current CI status of a repo using GitHub's Statuses API

Downloads

3

Readme

github-ci-status

github-ci-status will tell you whether the currently checked out state of a Git repository was tested by a CI on GitHub, using the GitHub Statuses API.

The output can look like this:

λ ci
Checking keybase/client:5ab4553d88

✔ The Travis CI build passed
✔ AppVeyor build succeeded
✔ Your tests passed on CircleCI!
✔ CI tests passed

λ echo $?
0

Or this:

λ ci
Checking keybase/client:1280c0238c

✔ Your tests passed on CircleCI!
✖ AppVeyor build failed
✖ The Travis CI build failed
✖ CI tests failed

λ echo $?
2

Or this:

λ ci --required-tests 3
Checking keybase/client:1207f99be4

✔ Your tests passed on CircleCI!
✔ The Travis CI build passed
⚠ The required number of tests weren't run (2 vs 3)

λ echo $?
4

Usage

Just run ci inside your repo. The repo should have the origin remote set to GitHub. Only works on public repos at the moment, but it would be easy to support private and GitHub Enterprise repos too.