backfill-performance-logger 3.0.3-alpha.0

Backfill Performance Logger

backfill-performance-logger@3.0.3-alpha.0 was published on 2020-03-25. 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 backfill-performance-logger versions · Permanent reference to 3.0.3-alpha.0 · Latest release

Package specifications

Version	3.0.3-alpha.0
License declaration	MIT
Published	2020-03-25T12:39:14.544Z
Node.js requirement	Not declared
Type declarations	Not declared
Runtime dependency count	3
Peer requirement count	0
Optional dependency count	0
Minified size	Measurement not available yet
Minified + gzip	Measurement not available yet
Unpacked distribution size	125.97 KiB
Published file count	9
Package type	Not declared
ES module entry	Not declared
Default entry	lib/index.js
Side effects declaration	Not declared
Direct advisories	0
Resolved graph dependencies	16
Repository stars	164
Repository forks	31

Install backfill-performance-logger 3.0.3-alpha.0

npm install backfill-performance-logger@3.0.3-alpha.0
pnpm add backfill-performance-logger@3.0.3-alpha.0
yarn add backfill-performance-logger@3.0.3-alpha.0

Runtime dependencies

backfill-generic-logger ^3.0.1-alpha.0
filenamify ^4.1.0
fs-extra ^8.1.0

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.

ansi-styles@4.3.0 — indirect
backfill-generic-logger@3.0.1-alpha.0 — direct
chalk@3.0.0 — indirect
color-convert@2.0.1 — indirect
color-name@1.1.4 — indirect
escape-string-regexp@1.0.5 — indirect
filename-reserved-regex@2.0.0 — indirect
filenamify@4.3.0 — direct
fs-extra@8.1.0 — direct
graceful-fs@4.2.11 — indirect
has-flag@4.0.0 — indirect
jsonfile@4.0.0 — indirect
strip-outer@1.0.1 — indirect
supports-color@7.2.0 — indirect
trim-repeated@1.0.0 — indirect
universalify@0.1.2 — indirect

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.

Dangerous-Workflow	10/10 — no dangerous workflow patterns detected
Code-Review	0/10 — Found 1/14 approved changesets -- score normalized to 0
Maintained	0/10 — project is archived
Security-Policy	10/10 — security policy file detected
CII-Best-Practices	0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions	0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts	10/10 — no binaries found in the repo
Pinned-Dependencies	10/10 — all dependencies are pinned
License	10/10 — license file detected
Fuzzing	0/10 — project is not fuzzed
Branch-Protection	4/10 — branch protection is not maximal on development and all release branches
SAST	9/10 — SAST tool detected but not run on all commits

Evidence and freshness

https://registry.npmjs.org/backfill-performance-logger/3.0.3-alpha.0 — retrieved 2026-10-31T22:17:50.585Z
https://api.deps.dev/v3/systems/npm/packages/backfill-performance-logger/versions/3.0.3-alpha.0 — retrieved 2026-10-31T22:17:51.012Z
https://api.deps.dev/v3/systems/npm/packages/backfill-performance-logger/versions/3.0.3-alpha.0:dependencies — retrieved 2026-10-31T22:17:51.036Z
https://api.deps.dev/v3/projects/github.com%2Fmicrosoft%2Fbackfill — retrieved 2026-10-31T22:17:51.514Z