lru_map

Finite key-value map using the Least Recently Used (LRU) algorithm where the most recently used objects are keept in the map while less recently used items are evicted to make room for new ones.

lru_map@0.4.1 was published on 2020-10-22. Its manifest declares 0 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 lru_map versions · Permanent reference to 0.4.1

Package specifications

Version0.4.1
License declarationMIT
Published2020-10-22T16:32:14.949Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size27.29 KiB
Published file count6
Package typeNot declared
ES module entryNot declared
Default entrydist/lru.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars796
Repository forks88

Install lru_map 0.4.1

npm install lru_map@0.4.1
pnpm add lru_map@0.4.1
yarn add lru_map@0.4.1

Runtime dependencies

  • None declared

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-Review1/10 — Found 4/27 approved changesets -- score normalized to 1
    Pinned-Dependencies3/10 — dependency not pinned by hash detected -- score normalized to 3
    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
    Dangerous-Workflow10/10 — no dangerous workflow patterns detected
    Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Fuzzing0/10 — project is not fuzzed
    Security-Policy0/10 — security policy file not detected
    License10/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