caterpillar-filter 3.1.0

Filter out undesired log levels from your Caterpillar logger stream

caterpillar-filter@3.1.0 was published on 2019-01-01. Its manifest declares 1 runtime dependency and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.12.

Deprecated: inlined within caterpillar: https://github.com/bevry/caterpillar/blob/master/HISTORY.md#v600-2020-july-24

All caterpillar-filter versions · Permanent reference to 3.1.0 · Latest release

Package specifications

Version3.1.0
License declarationMIT
Published2019-01-01T09:38:46.396Z
Node.js requirement>=0.12
Type declarationsNot declared
Runtime dependency count1
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size26.76 KiB
Published file count8
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies3
Repository stars5
Repository forks0

Install caterpillar-filter 3.1.0

npm install caterpillar-filter@3.1.0
pnpm add caterpillar-filter@3.1.0
yarn add caterpillar-filter@3.1.0

Runtime dependencies

Peer requirements

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-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License9/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