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

@orangebeard-io/newman-reporter-orangebeard

v2.0.5

Published

A run time test run listener for Postman (Newman)

Downloads

12

Readme

Installation

Install the npm package

npm install @orangebeard-io/newman-reporter-orangebeard

Configuration

Create orangebeard.json (in your collection's folder (or above))

{
	"endpoint": "https://XXX.orangebeard.app",
	"accessToken": "00000000-0000-0000-0000-00000000",
	"project": "my_project_name",
	"testset": "My Test Set Name"
}

Running

From the command line:

newman run ./postman-collection.json -r @orangebeard-io/orangebeard

Or configure using the CLI (without orangebeard.json):

newman run ./collection.json -r @orangebeard-io/orangebeard \
--reporter-@orangebeard-io/orangebeard-endpoint=https://my.orangebeard.app \
--reporter-@orangebeard-io/orangebeard-token=00000000-0000-0000-00000000 \
--reporter-@orangebeard-io/orangebeard-testset=testset_name \
--reporter-@orangebeard-io/orangebeard-project=project_name \
--reporter-@orangebeard-io/orangebeard-description=description \
--reporter-@orangebeard-io/orangebeard-attributes=key:value;secondkey:secondvalue;singleTag

Note: Description and attributes are optional.

Or programmatically:

const newman = require('newman');

newman.run(
  {
    collection: './collection.json',
    reporters: '@orangebeard-io/orangebeard',
    reporter: {
      '@orangebeard-io/orangebeard': {
        endpoint: 'https://my.orangebeard.app',
        token: '00000000-0000-0000-0000-000000000000',
        testset: 'testset_name',
        project: 'project_name',
        description: 'description',
        attributes: [
          {
            key: 'key',
            value: 'val',
          },
          {
            value: 'singleTag',
          },
        ],
      },
    },
  },
  function (err) {
    if (err) {
      throw err;
    }
    console.log('collection run complete!');
  },
);

Using Postman CLI JSON reports

If you use the Postman CLI with its JSON reporter, you can import those JSON reports into Orangebeard using the CLI utility that ships with this package.

1. Generate a JSON report with Postman CLI

From your API project, run the Postman CLI with JSON output enabled (example):

postman collection run ./VAmPI.postman_collection.json \
  --reporters json \
  --reporter-json-export ./postman-cli-reports/VAmPI-report.json

This produces a JSON file containing a run object with executions, similar to the examples under example_pm_collection/postman-cli-reports/ in this repository.

2. Report the JSON run to Orangebeard

From this package's directory (with your Orangebeard configuration already set up, e.g. via orangebeard.json or environment):

npm run report:postman-cli-json -- ./example_pm_collection/postman-cli-reports/VAmPI-report.json

Or, if the package is installed globally or as a project dependency:

postman-cli-to-orangebeard ./example_pm_collection/postman-cli-reports/VAmPI-report.json

The utility will:

  • Create an Orangebeard test run using the same automatic configuration logic as the Newman reporter.
  • Create one Orangebeard test per request in the JSON report.
  • Log request and response metadata in Markdown, including headers and JSON/XML bodies in fenced code blocks.
  • Map Postman tests/assertions to Orangebeard steps, attaching error messages and stack traces when they fail.
  • Use the timing information from the report to reconstruct start/end timestamps per test and for the entire run.