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

pcaps-mount

v1.2.0

Published

Mounts pcaps received from socket

Downloads

6

Readme

pcaps-mount

A node.js library for catching Buffers through a socket, and writing them down on a pcap.

Description

This library was written with the only goal of facilitating packet gathering for the Teccon II project, therefore it does some pretty specific stuff.

So, what it does, it listens to a WebSocket server, gets a Buffer out of it, chops the buffer into packets with a specific length (default 1424) and writes it into a .pcap for a certain amount of time.

As said, quite specific

Instalation

Initialy, this library was thought to be used as a CLI. So it's likely for you to want to install it like that

npm i -g pcaps-mount

That way, you are able to use it as CLI.

But, of course, if you want to use it as dependency, you can go with

npm i pcaps-mount

Using the CLI

So, there are two usage for the CLI. A method that just captures a single pcap, and another that just keeps listening to the WebSocket and making new pcaps. Both will be explained below.

  • mount-pcap

    The mount-pcap command has the following usage specs :

    Usage : -u <uri> -t <capture-time> -o <output-path>
    
    Opções:
    --help               Shows help                                                                   [boolean]
    --version            Shows version                                                                [boolean]
    -u, --uri            Web Socket server to listen to                                     [string] [required]
    -t, --capture-time   Capture time, in seconds                                           [number] [required]
    -o, --output-path    Output path for the pcap file                                      [string] [required]
    -l, --packet-length  Packet length for each individual packet within the Buffer    [number] [default: 1424]
    -v, --verbose        Activates verbose                                           [boolean] [default: false]

    So, say you want to capture the packets from a local WebSocket server for 30 seconds and save it in the working directory, you would run something like this :

    pcap-mount -u ws://localhost:3000 -t 5 -o ./

  • listen-pcaps

    In a similar way, the listen-pcaps usage goes like this:

    Usage : -u <uri> -t <capture-time> -o <output-path>
    
    Opções:
    --help               Shows help                                                                   [boolean]
    --version            Shows version                                                                [boolean]
    -u, --uri            Web Socket server to listen to                                     [string] [required]
    -t, --capture-time    Capture time for each pcap, in minutes                            [number] [required]
    -o, --output-path    Output path for the pcap file                                      [string] [required]
    -l, --packet-length  Packet length for each individual packet within the Buffer    [number] [default: 1424]
    -v, --verbose        Activates verbose                                           [boolean] [default: false]

    So, if you want to continualy hear the arriving buffers, writing one .pcap each 2 minutes, and saving them in the working directory, you would run something like this :

    listen-pcaps -u ws://localhost:3000 -t 2 -o ./