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

@prodgator/report

v3.25.0

Published

Send CI job summaries, test results, attestations and artifacts to Prodgator, authenticated with the CI system's OIDC token

Readme

@prodgator/report

Shared report client for the Prodgator GitHub action, GitLab component and Bitbucket pipe. User docs: the Run reports guide.

Command line

prodgator-report runs in GitLab CI or Bitbucket Pipelines, reads the job's OIDC token, and sends a report to Prodgator. On GitHub Actions, use the prodgator/prodgator-action action instead.

Options can be set as a CLI flag, a PRODGATOR_-prefixed environment variable, or (only with --pipe) an unprefixed pipe variable. A flag wins over a pipe variable, which wins over the PRODGATOR_ variable, which wins over the default.

On Azure Pipelines, a script step reads PRODGATOR_URL and PRODGATOR_ALLOW_CUSTOM_URL from pipeline variables, so do not make them settable at queue time. The Marketplace task ignores them and takes inputs only.

| Option | CLI flag | Env (GitLab, any shell) | Pipe variable | |---|---|---|---| | prodgatorUrl | --prodgator-url | PRODGATOR_URL | PRODGATOR_URL | | audience | --audience | PRODGATOR_AUDIENCE | AUDIENCE | | summary | --summary | PRODGATOR_SUMMARY | SUMMARY | | summaryFile | --summary-file | PRODGATOR_SUMMARY_FILE | SUMMARY_FILE | | name | --name | PRODGATOR_NAME | NAME | | jobName | --job-name | PRODGATOR_JOB_NAME | (none: Bitbucket uses the step name) | | matrix | --matrix | PRODGATOR_MATRIX | MATRIX | | junit | --junit | PRODGATOR_JUNIT | JUNIT | | artifacts | --artifacts | PRODGATOR_ARTIFACTS | ARTIFACTS | | attestations | --attestations | PRODGATOR_ATTESTATIONS | ATTESTATIONS | | redactVariables | --redact-variables | PRODGATOR_REDACT_VARIABLES | REDACT_VARIABLES | | failOnError | --fail-on-error | PRODGATOR_FAIL_ON_ERROR | FAIL_ON_ERROR | | gate | --gate | PRODGATOR_GATE | GATE | | gateTimeoutMinutes | --gate-timeout | PRODGATOR_GATE_TIMEOUT | GATE_TIMEOUT | | blame | --blame / --no-blame | PRODGATOR_BLAME | (none: set PRODGATOR_BLAME: 'false') | | tokenVariable | --token-variable | PRODGATOR_TOKEN_VARIABLE | (none) |

GitLab CI example, reporting from its own short job:

unit-tests:
  image: node:22
  id_tokens:
    PRODGATOR_ID_TOKEN:
      aud: https://api.prodgator.io
  script:
    - npm ci && npm test
  after_script:
    - npx --yes @prodgator/report@1 --junit 'test-results/*.xml'