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

@testream/go-reporter

v1.0.1

Published

Run Go tests, publish CTRF results, and send source evidence and CI metadata to Testream and Jira.

Readme

@testream/go-reporter: Go test reporting for Jira

@testream/go-reporter runs Go tests and publishes the results to Testream as durable, Jira-visible evidence. Your Go test suite remains the execution source; Testream adds failure inspection, CI context, and run history without requiring duplicate manual cases.

What the reporter sends to Testream and Jira

  • Passed, failed, skipped, and pending Go test results
  • Failure status, duration, and suite structure
  • Source snippets and test locations when available
  • Branch, commit, build, environment, and CI metadata
  • Test-run history for Jira and release reviews

Install and run in CI

- uses: actions/setup-go@v5
  with:
    go-version: '1.24'

- uses: actions/setup-node@v4
  with:
    node-version: '20'

- run: npm install -g @testream/go-reporter

- run: |
    testream-go \
      --api-key "${{ secrets.TESTREAM_API_KEY }}" \
      --fail-on-error

Store TESTREAM_API_KEY as a protected CI secret. The command works in GitHub Actions, GitLab CI/CD, Azure Pipelines, Jenkins, and other command-based CI systems.

Go evidence in CI/CD

The reporter publishes structured Go test results while your existing Go project and CI workflow remain unchanged. Testream connects test failures and run context to the delivery work teams already manage in Jira.

Go test failures remain CI failures after the report is published. Upload failures are non-fatal by default; use --fail-on-error when an upload failure should also fail the command.

Frequently asked questions

Do we need to recreate automated tests as manual Jira cases?

No. Your Go test suite remains the code-first execution source. Testream publishes its results for Jira users without requiring a duplicate manual case for every automated test.

Does the reporter replace the Go test runner?

No. It runs with your existing Go tests and adds Testream reporting around the results they produce.

Official Testream resources