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

@adobe/cci-test-aggregator

v1.1.28

Published

CircleCI Test Aggregator

Downloads

115

Readme

CircleCI Test Aggregator

Aggregates test results from multiple CircleCI pipeline steps

When running builds that depend on external pipelines to complete (such as Project Helix Smoke Tests) it is inconvenient to find the correct URL for the workflow in the CircleCI log messages, open it, find the failed build job and check the test results there. With this utility you can use the CircleCI API to aggregate test results from external pipeline runs (multiple jobs) and report them in the JUnit test format that CircleCI expects.

Status

codecov CircleCI GitHub license GitHub issues LGTM Code Quality Grade: JavaScript semantic-release

Installation

$ npm install @adobe/cci-test-aggregator

Usage

$ export SMOKE_TEST_TOKEN="<your circleci token here>"
# Replace the URL with your Pipeline URL
$ npx @adobe/cci-test-aggregator https://circleci.com/api/v2/pipeline/477b38d1-faf7-4156-a48a-9aba71acbc4a/workflow
$ cat junit/junit.xml

You can now use the junit folder as test artifact in CircleCI.

Development

Build

$ npm install

Test

$ npm test

Lint

$ npm run lint