@verdaccio/file-locking 9.7.0

library that handle file locking

@verdaccio/file-locking@9.7.0 was published on 2020-06-24. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=8.

All @verdaccio/file-locking versions · Permanent reference to 9.7.0 · Latest release

Package specifications

Version9.7.0
License declarationMIT
Published2020-06-24T07:32:52.981Z
Node.js requirement>=8
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size16.77 KiB
Published file count14
Package typeNot declared
ES module entryNot declared
Default entrylib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies2
Repository stars17940
Repository forks1477

Install @verdaccio/file-locking 9.7.0

npm install @verdaccio/file-locking@9.7.0
pnpm add @verdaccio/file-locking@9.7.0
yarn add @verdaccio/file-locking@9.7.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-Review7/10 — Found 16/21 approved changesets -- score normalized to 7
Maintained10/10 — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy10/10 — security policy file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns 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
Branch-Protection6/10 — branch protection is not maximal on development and all release branches
Packaging10/10 — packaging workflow detected
SAST9/10 — SAST tool detected but not run on all commits
Pinned-Dependencies2/10 — dependency not pinned by hash detected -- score normalized to 2

Evidence and freshness