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 🙏

© 2024 – Pkg Stats / Ryan Hefner

healthchecks-external

v1.2.4

Published

Minimal server health checks framework

Downloads

7

Readme

HealthChecks-External

NPM

Downloads per month npm version Build Status Known Vulnerabilities

[[TOC]]


Install

Install with npm:

  npm install healthchecks-external

Basic Usage

Require the module:

HealthChecks = require 'healthchecks-external'

Start using HealthChecks...

healthCheck = new HealthChecks()

check = ->
  res = await healthCheck.checkPortIsOpen 'google.com', 443
  return res

status = if check() then 'UP' else 'DOWN'
console.log "Google is #{status}"

Supported methods

Several checks are available:

addProfile

Add a complete TLS/SSL profile, useful for requests against client authentified endpoints.

A profile object is composed with:  
- key: the private certificate path
- cert: the public certificate path
- ca: the certificate authority path  
  • Args: name (string), profile (object)
  • Return: boolean

checkPortIsOpen

Verify that a remote TCP port is open.

  • Args: host (string), port (number)
  • Return: boolean

checkPortLatency

Verify latency of a remote TCP port (in ms).

  • Args: host (string), port (number)
  • Return: boolean

checkCertificateDN

Verify DN of remote peer certificate.

  • Args: host (string), port (number) [, profile_name (string)]
  • Return: array of issuer (string)

checkCertificateIssuer

Verify ~~complete~~ chain of remote peer certificate issuers.

  • Args: host (string), port (number) [, profile_name (string)]
  • Return: array of issuer (string)

checkCertificateExpiration

Verify remote peer certificate expiration date.

  • Args: host (string), port (number) [, profile_name (string)]
  • Return: expiration_date (string)

checkAPICallContent

Verify API call (using JSON POST method by default).

  • Args: url (string), method (string) [, profile_name (string)]
  • Return: answer (object) {status: 'status_code', data: data}

checkWebPageContent

Verify Web page content (using GET method by default).

  • Args: url (string), method (string) [, profile_name (string)]
  • Return: answer (object) {status: 'status_code', data: data}

checkClientAuthentication

Verify remote server is enforcing client authentication or not.

  • Args: host (string), port (number)
  • Return: boolean

Developers

If you want to contribute to this project you are more than welcome !

Run tests

npm test

Please use Coffeescript for development language

Compilation

Use coffeescript to compile your tests

coffee -wc ./test

Use npm to compile your changes in HealthChecks

npm run build

Publish

The NPM publishing is automated, just merge PR from develop into master in order to publish corresponding package in NPM and GitHub repositories.

TODO

  • [ ] write better doc
  • [ ] support full certificate chain validation of issuers
  • [ ] add UDP support
  • [ ] add vulners check
  • [ ] add some crazy checks
  • [ ] unittests vulners check