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

@axiomify/logger

v6.3.3

Published

Structured request/response logging for Axiomify with recursive PII masking.

Downloads

1,119

Readme

@axiomify/logger

npm version codecov OpenSSF Scorecard License: MIT

Structured request/response logging for Axiomify with PII field masking and configurable log levels.

Install

npm install @axiomify/logger

Quick start

import { useLogger } from '@axiomify/logger';

useLogger(app, {
  level: 'info',
  sensitiveFields: [
    'password',
    'authorization',
    'x-api-key',
    'token',
    'cardNumber',
    'cvv',
  ],
});

Options

| Option | Type | Default | Description | | ------------------------ | ---------------------------------------- | -------- | ------------------------------------------------------------------------------------ | | level | 'debug' \| 'info' \| 'warn' \| 'error' | 'info' | Minimum log level. Messages below this level are suppressed. | | sensitiveFields | string[] | [] | Field names (case-insensitive) to mask in headers and body. Masked as '****'. | | beautify | boolean | false | Colorised, human-readable output for local development. JSON in production. | | includeHeaders | boolean | false | Include request headers in log entries. Enable only when the log pipeline is secure. | | includeParams | boolean | false | Include request route parameters (req.params) in log entries. | | includeQuery | boolean | false | Include request query parameters (req.query) in log entries. | | includeBody | boolean | false | Include request body (req.body) in log entries. | | includeResponseHeaders | boolean | false | Include response headers in log entries. | | includeResponsePayload | boolean | false | Include response payload/data in log entries. | | includePayload | boolean | false | Alias for includeResponsePayload. | | includeState | boolean | false | Include request state (req.state) in log entries. |

Log output

Each request produces two log entries:

On onRequest — incoming request:

{
  "level": "info",
  "requestId": "abc-123",
  "method": "POST",
  "path": "/users",
  "ip": "10.0.0.1",
  "ts": "2024-01-01T00:00:00.000Z"
}

On onPostHandler — response sent:

{
  "level": "info",
  "requestId": "abc-123",
  "status": 201,
  "latencyMs": 12,
  "ts": "2024-01-01T00:00:00.001Z"
}

On onError — handler threw:

{
  "level": "error",
  "requestId": "abc-123",
  "error": "Validation failed",
  "status": 400,
  "latencyMs": 3
}

Masking

Masking is recursive — it traverses nested objects and arrays:

useLogger(app, { sensitiveFields: ['password', 'token'] });

// Request body { email: '[email protected]', password: 'secret123', nested: { token: 'xyz' } }
// Logged as:   { email: '[email protected]', password: '****', nested: { token: '****' } }

Field names are matched case-insensitively. Masking depth is bounded to prevent stack overflow on adversarially deep objects.

Development mode

useLogger(app, {
  level: 'debug',
  beautify: true, // coloured output with readable timestamps
  includeHeaders: true,
  includeParams: true,
  includeQuery: true,
  includeBody: true,
  includeResponseHeaders: true,
  includeResponsePayload: true,
  includeState: true,
});

Custom log destination

The logger writes to process.stdout. To redirect to a log aggregator (Datadog, Loki, etc.), pipe stdout at the process level:

node server.js | my-log-shipper

Or replace process.stdout.write before calling useLogger for programmatic control.