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

uptime-check

v5.0.0-next.1

Published

Node website uptime checker (built on top of node-libcurl)

Readme

Uptime check

npm version

Checks uptime status of given url and provided keyword (optional).

How it works

Makes simple fetch requests, gathers data on response and if requested also is looking for a keyword inside the document body.

If http code (response) is 2xx website is considered "up". If there is a keyword given for search, but the keyword cannot be found in the document body, website is considered "down".

v5 migration

From version 5 this package becomes 0-depencency. With that got got replaced with native fetch.

For the sake of maintenance ease, node@24 or higher is required.

To migrate please check the new function signature and returned result:

declare module "uptime-check" {
  export interface UptimeCheckResult {
    success: boolean; // true if test passed, false if failed
    statusCode: number;
    didRedirect: boolean;
    effectiveUrl: string; // last url in the redirects chain
    totalTime: number; // total request time
    thrownError?: Error; // in case of fetch error, original Error object
    thrownErrorCode?: string; // in case of a request error, e.g. ETIMEDOUT, CERT_HAS_EXPIRED, when provided
  }

  export interface UptimeCheckOptions {
    url: string;
    keyword?: string; // defaults to null
    allowRedirects: boolean; // defaults to false
    headers?: object;
  }

  export default function check(o: UptimeCheckOptions): Promise<UptimeCheckResult>;
}

v4 migration

From version 4 there is no userAgent option any more. If you used this, please migrate to:

check({
  headers: {
      'User-Agent': 'Your custom UA string',
  }
});

Example usage

import check from 'uptime-check';
const result = await check({
  url: 'https://example.com',
  keyword: 'Example',
  allowRedirects: true,
});

const isUp = result.success; // true or false