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

xunithub

v0.3.0

Published

Parsing xunit reports, and posting them as Github comments

Readme

xunithub

Introduction

xunithub tries to save time you spend in analyzing test failures with your PR build. it simply goes through xunit report folder, parses all report files to find test failures, and then post those failures to github as PR comment.Its completely test framework agnostic, and only relies on xunit reporting standard. if your framework outputs xunit reports, and you use github as your code repository,you can use xunithub.

Usage

xunithub -g https://api.github.com/repos/(org/repo) -k (Github Access Token) -p (Github PR ID) -t (Xunit Test folder)

xunithub -g https://api.github.com/repos/proverma/arrow -k XXXXXXXXXXXXXXXXXXXXXXX -p 4 -t ~/Work/test-xunit

Usage without API key

If you do not want to use an API key, you can use a username and password, or username and MFA token, by including it in the repo url like so:

xunithub -g https://username:[email protected]/repos/(org/repo) -p (Github PR ID) -t (Xunit Test folder)

xunithub -g https://proverma:[email protected]/repos/proverma/arrow -p 4 -t ~/Work/test-xunit

Example Report

Here is an example of what a report looks like in Github:

Failures

YourTestSuite.xml (1)

  • Test Class Name : YourTestSuite - YourTest

  • Test Case Name : should not fail

  • Failure Message :

undefined is not an object: myObject.myProperty

___
___

## Help

### How to create Github Access token

https://help.github.com/articles/creating-an-access-token-for-command-line-use/