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

log-obfuscator

v1.0.0

Published

A CLI tool to obfuscate sensitive information (IP, email, credit card, etc.) in log files or directories before sharing.

Readme

Log-Obfuscator

Before submitting user logs (such as Nginx logs or application error logs) to analysis tools or third parties for debugging, it is essential to remove sensitive information (IP addresses, emails, credit card numbers). Manually editing large log files is time-consuming and unsafe.

🚀 Tool Idea: Log-Obfuscator

Features

  • Accepts a log file path or directory.
  • Identifies and obfuscates sensitive data using built-in or user-provided regular expression patterns, without affecting the log structure.
    (For example, replaces IP addresses with [IP_REDACTED], emails with [EMAIL_REDACTED].)
  • Outputs the obfuscated logs to a new file or stream.

User Pain Point Solved

Automates the critical step of data privacy and compliance, ensuring sensitive information is not leaked to debugging environments or analysis services.

Why Node.js

Node.js provides excellent stream processing capabilities, allowing efficient handling of very large log files (GB-level) without loading the entire file into memory.


Usage

Install

Clone this repo or copy the tool directory, then install dependencies if needed:

npm install

Command Line

node index.js <input> [options]

Or, if you add a bin entry and install globally:

log-obfuscator <input> [options]

Arguments

  • <input>: Path to a log file or directory to process.

Options

  • -o, --output <output>: Output file or directory. If not specified, output will be printed to stdout.
  • -p, --patterns <patternFile>: Path to a custom patterns JSON file for additional or custom obfuscation rules.

Examples

Obfuscate a single log file and print to console:

node index.js example.log

Obfuscate a log file and write to a new file:

node index.js example.log -o obfuscated.log

Obfuscate all logs in a directory and output to another directory:

node index.js ./logs -o ./logs-obfuscated

Use custom patterns:

node index.js example.log -p my-patterns.json -o obfuscated.log

Custom Patterns File Example

my-patterns.json:

[
  {
    "name": "Phone Number",
    "regex": "\\b\\d{3}[-.]?\\d{3}[-.]?\\d{4}\\b",
    "replacement": "[PHONE_REDACTED]"
  }
]

Example

Input:

2023-10-08 12:00:01 INFO User login from 192.168.1.10, email: [email protected]
2023-10-08 12:01:15 ERROR Payment failed for user [email protected], card: 4111 1111 1111 1111

Output:

2023-10-08 12:00:01 INFO User login from [IP_REDACTED], email: [EMAIL_REDACTED]
2023-10-08 12:01:15 ERROR Payment failed for user [EMAIL_REDACTED], card: [CREDIT_CARD_REDACTED]