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

@coe-sys/pims

v1.0.1

Published

The shared NestJS support library behind the PIMS gateways: API-key auth, the proxy middlewares, request/response logging with redaction, and the process safety nets.

Readme

@coe-sys/pims

The shared NestJS support library behind the PIMS gateways: API-key auth, the proxy middlewares, request/response logging with redaction, and the process safety nets.

Install

npm install @coe-sys/pims

Requires NestJS ^11 and Node >= 20. The @nestjs/* packages are peer dependencies, so npm will refuse the install on NestJS 10 rather than nest a second framework copy. Do not force it onto NestJS 10 — a root-entry import then fails to boot with a MongooseCoreModule/ModuleRef error. Services still on 10 can use @coe-sys/pims/core (below) in the meantime; see the 0.8.0 notes in CHANGELOG.md.

Quickstart

import { Module } from '@nestjs/common';
import { PimsModule } from '@coe-sys/pims';

@Module({ imports: [PimsModule] })
export class AppModule {}

PimsModule needs MONGODB_URI in the environment, and reads API_LOG, KAFKA_LOG, GATEWAY_HOST and GATEWAY_KEY for the logging paths. It exports PimsService, LogService, ApiKeysService, ResponseInterceptorService and ApiLogInterceptor.

Customising what gets logged

LOG_POLICY decides which requests are logged and how they are redacted. The default (DefaultLogPolicy) excludes credential and payment routes and masks sensitive headers. Replace it through forRoot:

import { Module } from '@nestjs/common';
import { PimsModule, DefaultLogPolicy, LogRequestContext } from '@coe-sys/pims';

/** Keep payment traffic, but store the response as an audit marker only. */
class PaymentAuditLogPolicy extends DefaultLogPolicy {
  shouldLog(ctx: LogRequestContext): boolean {
    return /\/payment\//i.test(ctx.uri) || super.shouldLog(ctx);
  }

  redactResponse(): unknown {
    return '[AUDITED]';
  }
}

@Module({
  imports: [PimsModule.forRoot({ logPolicy: PaymentAuditLogPolicy })],
})
export class AppModule {}

Use forRootnot providers: [{ provide: LOG_POLICY, ... }] in your own module. Nest resolves providers per module, so a provider declared in your AppModule cannot shadow the one inside PimsModule: your APP_INTERCEPTOR-built ApiLogInterceptor would use your policy while the library's own writers kept the default, redacting the same request two different ways. forRoot replaces the provider inside PimsModule, which reaches all three writers.

Policy methods must be synchronous and must not throw — they run on the proxy response path.

@coe-sys/pims/core

The framework-free subset: no @nestjs/*, no mongoose, no http-proxy-middleware is pulled into the process. Importable from any NestJS version, or from an application that uses no framework at all.

import { shouldLogUri, redactBody, hashApiKey, convertKsqlResult } from '@coe-sys/pims/core';

Process safety nets

Node terminates on an unhandled rejection or uncaught exception by default, and this library floats promises that reach Mongo. Install the nets once at bootstrap so a Mongo hiccup becomes a logged incident instead of downtime:

import { installProcessSafetyNets } from '@coe-sys/pims';

installProcessSafetyNets();

Pair it with a container restart policy and alerting on those log lines.

Changelog

See CHANGELOG.md — including the breaking changes in 1.0.0.