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

@push.rocks/smartping

v1.0.10

Published

A utility for performing ping operations in Node.js environments.

Readme

@push.rocks/smartping

Small, typed, promise-first ping checks for Node.js. @push.rocks/smartping wraps the proven ping package behind a tiny TypeScript API, so service health checks, diagnostics, readiness probes, and connectivity tests stay easy to read.

It uses the system ping command through the underlying dependency, so it is designed for Node.js environments with a working platform ping utility available.

Issue Reporting and Security

For reporting bugs, issues, or security vulnerabilities, please visit community.foss.global/. This is the central community hub for all issue reporting. Developers who sign and comply with our contribution agreement and go through identification can also get a code.foss.global/ account to submit Pull Requests directly.

Install

pnpm add @push.rocks/smartping

What You Get

  • Smartping: a lightweight class for probing hosts.
  • ping(host, timeout?): returns the full ping response from the underlying ping.promise.probe(...) call.
  • pingAlive(host, timeout?): returns a boolean and converts ping failures into false.
  • TypeScript types, ESM exports, and direct async/await ergonomics.

Quick Start

import { Smartping } from '@push.rocks/smartping';

const smartping = new Smartping();

const response = await smartping.ping('127.0.0.1', 1);

console.log(response.alive); // true when the host responded
console.log(response.time);  // response time reported by the platform ping utility

API

new Smartping()

Creates a ping helper instance. The class is intentionally stateless, so you can create one per module, per service, or per check without setup.

import { Smartping } from '@push.rocks/smartping';

const smartping = new Smartping();

smartping.ping(host, timeout?)

Runs a ping probe and returns the full response object from ping.promise.probe(...).

const result = await smartping.ping('example.com', 2);

if (result.alive) {
  console.log(`${result.host} responded in ${result.time}`);
} else {
  console.log(`${result.host} did not respond`);
}

The timeout argument is passed to the underlying ping package as timeout, where it is documented as seconds. If omitted, @push.rocks/smartping uses its default value of 500.

smartping.pingAlive(host, timeout?)

Runs a ping probe and returns only the alive state.

const databaseHostIsReachable = await smartping.pingAlive('10.0.0.5', 1);

if (!databaseHostIsReachable) {
  throw new Error('Database host is not reachable');
}

pingAlive(...) is useful for health checks because it catches probe errors and returns false instead of throwing.

Usage Patterns

Service Health Check

import { Smartping } from '@push.rocks/smartping';

const smartping = new Smartping();

export const checkNetworkDependency = async () => {
  return smartping.pingAlive('api.internal.example', 1);
};

Diagnostics With Full Response Data

import { Smartping } from '@push.rocks/smartping';

const smartping = new Smartping();

const hosts = ['127.0.0.1', 'example.com', '10.0.0.5'];

for (const host of hosts) {
  const result = await smartping.ping(host, 1);
  console.log({
    host,
    alive: result.alive,
    output: result.output,
    time: result.time,
  });
}

Graceful Failure Handling

import { Smartping } from '@push.rocks/smartping';

const smartping = new Smartping();

try {
  const result = await smartping.ping('example.com', 1);
  console.log(result);
} catch (error) {
  console.error('Ping probe failed before producing a response:', error);
}

Use ping(...) when you need response details and want to decide how to handle errors yourself. Use pingAlive(...) when a simple true or false is the desired contract.

Runtime Notes

  • This package targets Node.js and ESM-based TypeScript projects.
  • The underlying ping package delegates to the operating system ping command.
  • Hosts can be DNS names or IP addresses accepted by the platform ping utility.
  • Timeout behavior is inherited from ping, including platform-specific details around system ping arguments.

License and Legal Information

This repository contains open-source code licensed under the MIT License. A copy of the license can be found in the LICENSE file.

Please note: The MIT License does not grant permission to use the trade names, trademarks, service marks, or product names of the project, except as required for reasonable and customary use in describing the origin of the work and reproducing the content of the NOTICE file.

Trademarks

This project is owned and maintained by Task Venture Capital GmbH. The names and logos associated with Task Venture Capital GmbH and any related products or services are trademarks of Task Venture Capital GmbH or third parties, and are not included within the scope of the MIT license granted herein.

Use of these trademarks must comply with Task Venture Capital GmbH's Trademark Guidelines or the guidelines of the respective third-party owners, and any usage must be approved in writing. Third-party trademarks used herein are the property of their respective owners and used only in a descriptive manner, e.g. for an implementation of an API or similar.

Company Information

Task Venture Capital GmbH
Registered at District Court Bremen HRB 35230 HB, Germany

For any legal inquiries or further information, please contact us via email at [email protected].

By using this repository, you acknowledge that you have read this section, agree to comply with its terms, and understand that the licensing of the code does not imply endorsement by Task Venture Capital GmbH of any derivative works.