log4js

Port of Log4js to work with node.

log4js@6.9.1 was published on 2023-03-08. Its manifest declares 5 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=8.0.

All log4js versions · Permanent reference to 6.9.1

Package specifications

Version6.9.1
License declarationApache-2.0
Published2023-03-08T15:58:16.480Z
Node.js requirement>=8.0
Type declarationsBundled declarations
Runtime dependency count5
Peer requirement count0
Optional dependency count0
Minified size36.15 KiB
Minified + gzip12.57 KiB
Unpacked distribution size155.98 KiB
Published file count33
Package typeNot declared
ES module entryNot declared
Default entry./lib/log4js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies10
Repository stars5823
Repository forks751

Install log4js 6.9.1

npm install log4js@6.9.1
pnpm add log4js@6.9.1
yarn add log4js@6.9.1

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review5/10 — Found 7/13 approved changesets -- score normalized to 5
Maintained10/10 — 16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Security-Policy10/10 — security policy file detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies1/10 — dependency not pinned by hash detected -- score normalized to 1
Fuzzing0/10 — project is not fuzzed
License9/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST8/10 — SAST tool detected but not run on all commits

Evidence and freshness