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

@remirage/secure-log

v1.0.9

Published

A utility for logging sensitive information securely by replacing specified values with asterisks.

Downloads

9

Readme

SecureLog

A TypeScript utility for securely logging messages by replacing sensitive information with a placeholder. This library provides a way to safely log information without exposing sensitive data.

Installation

You can install SecureLog using npm, yarn, or bun.

Using npm

npm install @remirage/secure-log

Using yarn

yarn add @remirage/secure-log

Using bun

bun add @remirage/secure-log

Usage

Import and Initialize

First, import the SecureLog class and initialize it with your mappings and optional configuration.

import { SecureLog, Mapping, Config } from '@remirage/secure-log';

// Example mappings
const mappings: Mapping[] = [
    { name: "password", value: "myPassword123" },
    { name: "apiKey", value: "abc123secretKey" }
];

// Optional configuration
const config: Config = {
    placeholder: "[REDACTED]",
    showMappingName: true,
    replaceConsoleLog: true,
    environment: {
        secure: true,
        ignoreKeys: ["SOME_SECRET_KEY"]
    }
};

// Initialize SecureLog
const secureLogInstance = new SecureLog(mappings, config);

Using console.secure

After initializing SecureLog, you can use console.secure to securely log messages. The console.secure method will replace any sensitive data based on the provided mappings and configuration.

// String data
console.secure("User login with password: myPassword123");

// Object data
console.secure({ message: "API call with apiKey: abc123secretKey" });

// Array data
console.secure(["Array element with password: myPassword123", "Another secret: abc123secretKey"]);

Overriding console.log

If replaceConsoleLog is set to true in the configuration, both console.log and console.secure will securely log messages.

// String data
console.log("User login with password: myPassword123");

// Object data
console.log({ message: "API call with apiKey: abc123secretKey" });

// Array data
console.log(["Array element with password: myPassword123", "Another secret: abc123secretKey"]);

Restore Original console.log

If needed, you can restore the original console.log functionality.

// Restore the original console.log
console.restoreLog();

Configuration Options

The SecureLog class accepts an optional configuration object with the following properties:

  • placeholder: A string to replace the sensitive data (default: "*****").
  • shouldReturn: A boolean indicating whether to return the modified data (default: false).
  • showMappingName: A boolean indicating whether to include the mapping name in the replacement (default: false).
  • replaceConsoleLog: A boolean indicating whether to override console.log to behave like console.secure (default: false).
  • environment: An object with the following properties:
    • secure: A boolean indicating whether to secure all environment variables (default: false).
    • ignoreKeys: An array of keys that will be ignored from the environment variables.

Example

Here's a complete example:

import { SecureLog, Mapping, Config } from '@remirage/secure-log';

// Example mappings
const mappings: Mapping[] = [
    { name: "password", value: "myPassword123" },
    { name: "apiKey", value: "abc123secretKey" }
];

// Optional configuration
const config: Config = {
    placeholder: "[REDACTED]",
    showMappingName: true,
    replaceConsoleLog: true,
    environment: {
        secure: true,
        ignoreKeys: ["SOME_SECRET_KEY"]
    }
};

// Initialize SecureLog
const secureLogInstance = new SecureLog(mappings, config);

// Using console.secure
console.secure("User login with password: myPassword123");
console.secure({ message: "API call with apiKey: abc123secretKey" });
console.secure(["Array element with password: myPassword123", "Another secret: abc123secretKey"]);

// Using console.log if replaceConsoleLog is true
console.log("User login with password: myPassword123");
console.log({ message: "API call with apiKey: abc123secretKey" });
console.log(["Array element with password: myPassword123", "Another secret: abc123secretKey"]);

// Restore the original console.log if needed
console.restoreLog();