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

policy-service

v1.0.0

Published

Process policies and submissions.

Readme

CI/CD pipelines

CI digital beesafe cicd

Policy Service

Welcome to policy service, a central hub for everything relating policies and submissions in Beesafe.

Running

Running the project the simple way

First you need to set your github access token to NPM_TOKEN (see .env.example). Windows:

set NPM_TOKEN=<your token>

Ubuntu:

export NPM_TOKEN=<your token>

To simply run the project and start hacking away, just run

docker-compose up --build

This will build the project and start it together with an instance of Postgres Database and a RabbitMQ service.

Changing the files in the project will reload the server, too.

Advanced

To start the project separately, you need to set up your .env file based on .env.example file. You need a postgres and a rabbitmq service running to be able to start the project.

To start the built version, you fist need to build it:

npm run build

and then

npm start

To start the live version, use:

npm run start:dev

Testing the message queue

To test if the messages work, you can enter the rabbit UI and search for the required queue http://localhost:15672/#/queues/%2F/policy-service

Default user-password: guest guest

Here, you can send a message with the body:

{
  "cmd": "policyService.test.testMessage",
  "content": ""
}

Testing

Tests cover the controllers, to run them use:

npm test