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

@mrackoa/plugin-report-portal-saas

v2.0.0

Published

Welcome to the report-portal plugin!

Readme

Report Portal Plugin

Welcome to the report-portal plugin!

ReportPortal is an open-source test automation dashboard that allows teams to manage and analyze test results from various test automation frameworks. It provides a centralized platform for aggregating test reports, offering real-time insights into test execution and helping to identify and address issues quickly.

The plugin integrates report portal instances to show projects and launches directly in backstage. This will be helpful for not just developers but also QEs

Getting started

Your plugin has been added to the example app in this repository, meaning you'll be able to access it by running yarn start in the root directory, and then navigating to /report-portal.

You can also serve the plugin in isolation by running yarn start in the plugin directory. This method of serving the plugin provides quicker iteration speed and a faster startup and hot reloads. It is only meant for local development, and the setup for it can be found inside the /dev directory.

Prequisite

Screenshots:

  • Dashboard for each entity in backstage:

    • A card for overall statistics panel / donut on overview tab image

    • [WIP] An entity tab that will show more detailed statistics for a specific launch.

  • A page to show details for each instance such as projects and launches file

Installation:

  • Run the following command in your backstage project

    yarn workspace app add @backstage-community/plugin-report-portal
  • Now import the components

    • open /packages/app/src/App.tsx and add the following code

      import { ReportPortalGlobalPage } from '@backstage-community/plugin-report-portal';
      
      export const AppBase = () => {
        // In <FlatRoutes> add the following route
        <Route path="/report-portal" element={<ReportPortalGlobalPage />} />;
      };
    • open /packages/app/src/components/Root/Root.tsx and add the following code

      import { ReportPortalIcon } from '@backstage-community/plugin-report-portal';
      import { IconComponent } from '@backstage/core-plugin-api';
      //...
      //...
      export const Root = ({ children }: PropsWithChildren<{}>) => (
        <SidebarPage>
      
          <!-- Add the link to route in your sidebar component -->
          <SidebarItem icon={ReportPortalIcon as IconComponent} to="report-portal" text="Report Portal" />
        </SidebarPage>
      )
    • To add a card on overview tab of entity page, open /packages/app/src/components/catalog/EntityPage.tsx and add the following code:

      import { ReportPortalOverviewCard } from '@backstage-community/plugin-report-portal';
      //...
      const overviewContent = (
        <Grid>
      
          <!-- add your card on overview -->
          <Grid item lg={4} md={6} xs={12}>
            <ReportPortalOverviewCard variant="gridItem" />
          </Grid>
        </Grid>
      );
  • Add the below configuration to your app-config.yaml file

    reportPortal:
      # Contact email template for support
      #  for example "mailto://[email protected]?subject=${subject}&body=${body}"
      #  where 'subject' and 'body' must be in url-encoded format
      supportEmailTemplate: ${REPORT_PORTAL_SUPPORT_MAIL}
    
      # Under integrations you can configure
      # multiple instances of report portal
      integrations:
        # host address of your instance
        # for e.g: report-portal.mycorp.com
        - host: ${REPORT_PORTAL_HOST}
    
          # Baser API url of your instance
          # for e.g: https://report-portal.mycorp.com/api/
          baseUrl: ${REPORT_PORTAL_BASE_URL}
    
          # Get the API key from profile page of your instance
          # for e.g: Bearer fae22be1-0000-0000-8392-de1635eed9f4
          token: ${REPORT_PORTAL_TOKEN}
    
          # (optional) Filter the projects by type
          # Default: "INTERNAL"
          filterType: 'INTERNAL'

Annotations:

Add the below annotations to catalog-info.yaml

metadata:
  annotations:
    reportportal.io/project-name: <your-project-name>
    reportportal.io/launch-name: <your-launch-name>

    # (optional) if host is not added in annotaions, first entry from app-config will be used
    reportportal.io/host: <your-report-portal-host>

Acknowledgments

This project wouldn't have been possible without the help of the following contributors:

  • Swapnil Jadhav
  • Nancy Jain
  • Shiwani Tummulwar
  • Suriya Prakash
  • Veerkumar Patil

Thank you for your invaluable contributions!