custom-logger 0.1.0

Highly customizable console logger for node.js. Supports templating of logged output, custom levels, custom log types, colored output, and custom date formatting. Really simple to set up and use.

custom-logger@0.1.0 was published on 2012-05-21. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.1.90.

All custom-logger versions · Permanent reference to 0.1.0 · Latest release

Package specifications

Version0.1.0
License declarationNot declared
Published2012-05-21T21:40:55.298Z
Node.js requirement>=0.1.90
Type declarationsNot declared
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entrylogger
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies2
Repository stars11
Repository forks3

Install custom-logger 0.1.0

npm install custom-logger@0.1.0
pnpm add custom-logger@0.1.0
yarn add custom-logger@0.1.0

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-Review2/10 — Found 4/20 approved changesets -- score normalized to 2
Binary-Artifacts10/10 — no binaries found in the repo
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness