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

turing-status

v0.50.0

Published

Aggregation of sub-statuses and express routes for an html and json status report.

Readme

turing-status

version license

Aggregation of sub-statuses and express routes for an html and json status report.

API

HTTP GET with Accept header application/json will yield to a json response. HTTP GET with Accept header text/html will yield to an html response.

Simply require turing-status and add the router to your turing-server.

const TuringStatus = require('turing-status');

app.use(new TuringStatus());

To add a sub-status call addStatusDetail(name, status, message) on you turing-server.

server.addStatusDetail('my-status-detail', 'OK', 'Everything is fine.');

Config

  • turing:server:routes:internal - The base-url of internal endpoints like health or status. (default: "/internal")
  • turing:status:route - The relative url of the status endpoint behind the internal route. (default: "/status")

Status Information Config

You can set additional status information by using the following configurations

Inside package.json
  • name - The name of the application.
  • description - A short description of the application's purpose.
  • version - The version of the application.
  • commit - The current commit hash of the application.
  • repository.url - The repository url of the application
  • dependencies - A list of the application's dependencies.
Inside Config
  • turing:status:application:group - The group of services, this application is part of.
  • turing:server:port - The server port.
  • turing:status:team:name - The name of the team.
  • turing:status:team:contact:technical - The technical contact.
  • turing:status:team:contact:business - The business contact.

Contributors

  • Benedikt Stemmildt
  • Jonathan Meyer

License

Apache-2.0