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

@redhat-cloud-services/frontend-components-inventory-vulnerabilities

v1.87.29

Published

[![Build Status](https://travis-ci.com/RedHatInsights/vulnerability-ui.svg?branch=master)](https://app.travis-ci.com/github/RedHatInsights/vulnerability-ui) [![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

lesamolesamojozefhartingerjozefhartingerkarelhalakarelhalahyperkidhyperkidflorkbrflorkbrjiridostaljiridostal

Keywords

Readme

Build Status semantic-release GitHub release codecov

Vulnerability UI

First time setup

Quick start

  1. Make sure you have Node.js and npm installed
  2. Run script to patch your /etc/hosts
  3. Make sure you are using Red Hat proxy

Comprehensive documentation

There is a comprehensive quick start guide in the Storybook Documentation to setting up an Insights environment.

Running locally

  1. Install dependencies with npm install
  2. Run development server with npm run start:proxy:beta
  3. Local version of the app will be available at https://stage.foo.redhat.com:1337/beta/insights/vulnerability/

Testing

Jest is used as the testing framework

  • npm run test - run all tests
  • npm run test -- testName - run tests for all components matching testName
  • npm run lint - run linter
  • npm run test:update - run all tests and update snapshots
  • npm run test:watch - run tests in watch mode

Deploying

Any push to the following branches will trigger a build in vulnerability-ui-build repository which will deploy to corresponding environment.

| Push to branch in this repo | Updated branch in build repo | Environment | Available at | :--------------------------- | :---------------------------- | :---------------- | :----------- | master | stage-beta | stage beta | https://console.stage.redhat.com/beta | stage-stable | stage-stable | stage stable | https://console.stage.redhat.com | prod-beta | prod-beta | production beta | https://console.redhat.com/beta | prod-stable | prod-stable | production stable | https://console.redhat.com

Internationalization

Translation keys

Translation keys are saved in messages.js.

Generating translation keys

Each time you add a new translation keys you need to run npm run translations, which will automatically generate JSON files for every language into locales/ folder based on the entries in the messages.js.

Using translated strings

There are two ways to use translated strings:

  1. With intl.formatMessage(messages.messageId)
  2. With <FormattedMessage {...messages.messageId}/>

Design System

This project uses Patternfly React.

Insights Components

This app imports components from Insights Front-end Components library. ESI tags are used to import Insights Chrome which takes care of the header, sidebar, and footer.

Versioning

This project uses Semantic Versioning. Release process is automated by using Semantic Release.