status-logger 3.1.1

print updating progress to console and stdout

status-logger@3.1.1 was published on 2017-09-26. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All status-logger versions · Permanent reference to 3.1.1 · Latest release

Package specifications

Version3.1.1
License declarationMIT
Published2017-09-26T22:01:13.960Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count3
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 entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies19
Repository stars2
Repository forks0

Install status-logger 3.1.1

npm install status-logger@3.1.1
pnpm add status-logger@3.1.1
yarn add status-logger@3.1.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-Review0/10 — Found 0/19 approved changesets -- score normalized to 0
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
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License0/10 — license file not detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Branch-Protection0/10 — branch protection not enabled on development/release branches

Evidence and freshness