@apify/log 2.0.0

Tools and constants shared across Apify projects.

@apify/log@2.0.0 was published on 2022-06-21. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @apify/log versions · Permanent reference to 2.0.0 · Latest release

Package specifications

Version2.0.0
License declarationApache-2.0
Published2022-06-21T14:20:44.096Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size99.65 KiB
Published file count14
Package typeNot declared
ES module entry./index.mjs
Default entry./index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies2
Repository stars20
Repository forks12

Install @apify/log 2.0.0

npm install @apify/log@2.0.0
pnpm add @apify/log@2.0.0
yarn add @apify/log@2.0.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-Review5/10 — Found 15/30 approved changesets -- score normalized to 5
Maintained10/10 — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Pinned-Dependencies2/10 — dependency not pinned by hash detected -- score normalized to 2
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
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Security-Policy0/10 — security policy file not detected
Branch-Protection5/10 — branch protection is not maximal on development and all release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Packaging10/10 — packaging workflow detected

Evidence and freshness