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

@atom-tech/report

v1.0.1

Published

Send a JUnit test report to asas from any CI pipeline.

Readme

@atom-tech/report

Sends a JUnit XML test report to asas, so automated results appear beside the ones people record by hand — same coverage figure, same history, same dashboard.

Nothing runs on the asas side. This posts a file your test runner already wrote.

Use it

- name: Send test results to asas
  if: always()
  run: npx --yes @atom-tech/report
  env:
    ASAS_URL: https://your-asas-host
    ASAS_PROJECT: your-project-id
    ASAS_TOKEN: ${{ secrets.ASAS_TOKEN }}

if: always() matters — without it the step is skipped exactly when tests failed, which is when the results are worth having.

Not on GitHub? It is the same command anywhere that runs node. GitLab, Jenkins, CircleCI, Buildkite and Vercel are all recognised.

It exits 0 when tests fail

On purpose. Your test runner already failed the build for that, one step earlier, and a reporting step that fails it a second time is the first thing anyone deletes. Pass --fail-on-test-failure if you would rather it did.

Settings

| Variable | | |---|---| | ASAS_TOKEN | Required. Create it in the project's Testing settings — it can only post results, it cannot read the project. | | ASAS_PROJECT | Required. The project id. | | ASAS_URL | Required. Your asas address. | | ASAS_BUILD | Optional. Defaults to the commit your CI is on. |

| Flag | | |---|---| | [file...] | The report. Left out, it is found automatically. | | --build <label> | What was under test. | | --dry-run | Show what would happen, write nothing. | | --fail-on-test-failure | Exit non-zero when a test failed. | | --token / --project / --url | Override the environment. |

Finding the report

With no path, it tries the conventional names first — junit.xml, test-results.xml, test-results/, reports/, build/test-results, target/surefire-reports — and only then walks the directory, skipping node_modules and friends. A sharded suite that writes several files has all of them sent.

Which runners

Anything that writes JUnit XML: Vitest, Jest, Playwright, Cypress, Mocha, PHPUnit, pytest, gotestsum, Maven, Gradle, RSpec, Karma.

Licence

MIT