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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@psastras/ovo

v1.3.8

Published

An alternate Zipkin UI

Readme

ovo

CircleCI codecov semantic-release

An alternate Zipkin UI. Zipkin is a distributed tracing system.

Screenshot

Running

npm

The easiest way to get up and running is to install viathe npm repository.

npm i -g @psastras/ovo
ovo # start up the server

Note that this starts expects Zipkin to be running on http://localhost:9411 (the default port that it starts on) the UI will start on port 8080 by default, navigate to http://localhost:8080 to view.

ovo accepts a custom port number via -p and a custom Zipkin host via -h (use the --help) argument for a list of supported options.

Node

To launch the server which will serve files out of dist/

yarn build # build the dist/ files
node index.js

Note that this expects Zipkin to be running on http://localhost:9411.

Docker

To quickly launch a demo the provided Docker compose file will launch both Zipkin and the UI.

yarn build # build the dist/ files
yarn build:server # build the server
docker-compose build
docker-compose up

Development

The preferred way to install dependencies is Yarn. This repo includes a yarn.lock file to ensure dependencies are consistent on install.

npm i -g yarn
yarn install

For most development purposes running the watch command should be enough

yarn watch

The watch commands starts a webpack development server at http://127.0.0.1:8080. It also watches test files in the test/ test directory for changes and runs the changed tests as necessary. When making changes to the source code in src/, relavant tests will be run as well.

To manually run tests and generate a code coverage report (and lint the code),

yarn test

To build a production distribution (minified, etc.)

yarn build

The production build files will be located in dist/.

This project uses Selenium for integration tests. Integration tests can be run using

yarn integrationtest