</>PackageGraphPackageGraph

proc-log

npmv7.0.0

just emit 'log' events on the process object

Safe to adopt

Yes — proc-log scores well across adoption, maintenance, weight, supply chain, and licensing. 52.4M downloads per week and 2 known dependents. Last published 124 days ago. 3 releases in the last 2 years.

  • AAdoption: grade A, Excellent.

    52.4M downloads per week and 2 known dependents.

  • BMaintenance: grade B, Good.

    Last published 124 days ago. 3 releases in the last 2 years.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 12 KB installed.

  • ASupply chain: grade A, Excellent.

    No install scripts, 4 maintainers, and a contained dependency surface.

  • ALicense: grade A, Excellent.

    ISC — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding proc-log to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

12 KB
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
node ^22.22.2 || ^24.15.0 || >=26.0.0
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the proc-log README.

jsFull README ↗
const { log, output, input, time } = require('proc-log')

Dependencies

Declared by proc-log v7.0.0. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (3)

@npmcli/eslint-config ^6.0.0@npmcli/template-oss 5.0.0tap ^16.0.1

Used by

Popular packages that depend on proc-log.

make-fetch-happennpm

Opinionated, caching, retrying fetch client

↓ 22.8M/wk◈ 1 dependents⚖ ISC
npm-package-argnpm

Parse the things that can be arguments to `npm install`

↓ 0/wk◈ 2 dependents⚖ ISC

Relationship graph

Dependencies (left) and dependents (right) of proc-log.

make-fetch-happennpm-package-argproc-log
proc-log dependencies dependents

Frequently installed together

negotiatornpm

HTTP content negotiation

↓ 183.3M/wk◈ 2 dependents⚖ MIT
minipass-pipelinenpm

create a pipeline of streams using Minipass

↓ 23.5M/wk◈ 2 dependents⚖ BlueOak-1.0.0TS
@gar/promise-retrynpm

Retries a function that returns a promise, leveraging the power of the retry module.

↓ 6M/wk◈ 1 dependents⚖ MITTS
validate-npm-package-namenpm

Give me a string and I'll tell you if it's a valid npm package name

↓ 0/wk◈ 1 dependents⚖ ISC
safe-buffernpm

Safer Node.js Buffer API

↓ 0/wk◈ 5 dependents⚖ MITTS
cacachenpm

Fast, fault-tolerant, cross-platform, disk-based, data-agnostic, content-addressable cache.

↓ 0/wk◈ 1 dependents⚖ ISC
@npmcli/agentnpm

the http/https agent used by the npm cli

↓ 0/wk◈ 1 dependents⚖ ISC
@npmcli/redactnpm

Redact sensitive npm information from output

↓ 0/wk◈ 1 dependents⚖ ISC
http-cache-semanticsnpm

Parses Cache-Control and other headers. Helps building correct HTTP caches and proxies

↓ 0/wk◈ 1 dependents⚖ BSD-2-ClauseTS
minipass-fetchnpm

An implementation of window.fetch in Node.js using Minipass streams

↓ 0/wk◈ 2 dependents⚖ MIT
ssrinpm

Standard Subresource Integrity library -- parses, serializes, generates, and verifies integrity metadata according to the SRI spec.

↓ 0/wk◈ 2 dependents⚖ ISC
semvernpm

The semantic version parser used by npm.

↓ 0/wk◈ 55 dependents⚖ ISC

Release history

3 releases in the last two years, typically about 164 days apart.

Recent versions of proc-log
VersionPublishedSizeLicense
7.0.0latest4 months ago12 KBISC
6.1.09 months ago12 KBISC
6.0.010 months ago12 KBISC
5.0.02 years ago12 KBISC
4.2.02 years ago12 KBISC
4.1.02 years ago12 KBISC
4.0.02 years ago7.1 KBISC
3.0.03 years ago5.1 KBISC
2.0.14 years ago5.1 KBISC
2.0.04 years ago4.9 KBISC
1.0.05 years ago3.4 KBISC

Overview

proc-log is an npm package that just emit 'log' events on the process object. It is extremely widely used, with about 52.4M downloads per week and 2 known dependents in the graph. The latest version is 7.0.0, released under the ISC license.

Who should use it

Teams working in the npm ecosystem who need just emit 'log' events on the process object and value a battle-tested, widely-adopted solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Large, well-established user base (52.4M weekly downloads).
  • Clear open-source license (ISC).
  • Lean dependency tree (3 direct dependencies).

Cons

  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

npm-cli-opsowlstronautreggisaquibkhan

Frequently asked questions

Should I use proc-log?

Yes — proc-log scores well across adoption, maintenance, weight, supply chain, and licensing. 52.4M downloads per week and 2 known dependents. Last published 124 days ago. 3 releases in the last 2 years.

How do I install proc-log?

Run `npm install proc-log` to add proc-log to your npm project.

What license is proc-log released under?

proc-log is distributed under the ISC license.

How popular is proc-log?

proc-log has approximately 52,376,579 downloads per week and 2 known dependent packages.

Is proc-log still maintained?

The most recent release of proc-log (v7.0.0) was published 4 months ago.

Does proc-log run install scripts?

No. proc-log does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.