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

@gibme/fping

v22.0.1

Published

A simple fping promise based wrapper

Readme

@gibme/fping

A simple promise-based wrapper around fping for Node.js.

Requirements

  • Node.js >= 22
  • fping must be installed on the system
    • Linux: sudo apt install fping
    • macOS: brew install fping

Installation

npm install @gibme/fping

or

yarn add @gibme/fping

Usage

import fping from '@gibme/fping';

const results = await fping(['1.1.1.1', '8.8.8.8']);

console.log(results);

With Options

const results = await fping(['1.1.1.1', '8.8.8.8'], {
    count: 3,
    timeout: 1000,
    retry: 5
});

for (const [host, result] of Object.entries(results)) {
    if (result) {
        console.log(`${host}: avg=${result.avg}ms, loss=${result.loss * 100}%`);
    }
}

Options

All options are optional. Defaults are shown below.

| Option | Type | Default | Description | |---|---|---|---| | bytes | number | 56 | Amount of ping data to send (minimum 40) | | backoff | number | 1.5 | Exponential backoff factor | | count | number | 1 | Number of pings to send per target (minimum 1) | | interval | number | 10 | Interval between ping packets in ms | | period | number | 1000 | Interval between pings to one target in ms | | retry | number | 3 | Number of retries | | random | boolean | true | Use random packet data | | timeout | number | 500 | Per-target initial timeout in ms | | digits | number | 3 | Decimal digits for latency values | | lossDigits | number | 4 | Decimal digits for loss percentage (minimum 2) |

Result

Each target returns a fping.Result object:

{
    target: string;    // The host that was pinged
    sent: number;      // Packets sent
    received: number;  // Packets received
    loss: number;      // Loss as a decimal (0.25 = 25%)
    avg: number;       // Average latency in ms
    min: number;       // Minimum latency in ms
    max: number;       // Maximum latency in ms
    stddev: number;    // Standard deviation of latencies
    times: number[];   // Individual ping times in ms
}

Documentation

https://gibme-npm.github.io/fping/

License

MIT