memoizee 0.2.6
Complete memoize/cache solution. Works with any type and length of function arguments
memoizee@0.2.6 was published on 2013-10-08. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.4.
All memoizee versions · Permanent reference to 0.2.6 · Latest release
Package specifications
| Version | 0.2.6 |
|---|---|
| License declaration | MIT |
| Published | 2013-10-08T13:24:15.938Z |
| Node.js requirement | >=0.4 |
| 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 | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | lib |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | 1777 |
| Repository forks | 62 |
Install memoizee 0.2.6
npm install memoizee@0.2.6 pnpm add memoizee@0.2.6 yarn add memoizee@0.2.6
Runtime dependencies
- es5-ext ~0.9.2
- event-emitter ~0.2.2
- next-tick 0.1.x
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.
- es5-ext@0.9.2 — direct
- event-emitter@0.2.2 — direct
- next-tick@0.1.0 — direct
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-Review | 1/10 — Found 3/30 approved changesets -- score normalized to 1 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/memoizee/0.2.6 — retrieved 2026-10-29T08:21:43.837Z
- https://api.deps.dev/v3/projects/github.com%2Fmedikoo%2Fmemoizee — retrieved 2026-10-29T08:19:28.456Z
- https://api.deps.dev/v3/systems/npm/packages/memoizee/versions/0.2.6 — retrieved 2026-10-29T08:21:44.364Z
- https://api.deps.dev/v3/systems/npm/packages/memoizee/versions/0.2.6:dependencies — retrieved 2026-10-29T08:21:44.387Z