memdown 1.4.1
An drop-in replacement for LevelDOWN that works in memory only
memdown@1.4.1 was published on 2017-10-04. Its manifest declares 6 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.
Deprecated: Superseded by memory-level (https://github.com/Level/community#faq)
All memdown versions · Permanent reference to 1.4.1 · Latest release
Package specifications
| Version | 1.4.1 |
|---|---|
| License declaration | MIT |
| Published | 2017-10-04T10:23:50.089Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 6 |
| 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 | memdown.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 7 |
| Repository stars | 286 |
| Repository forks | 31 |
Install memdown 1.4.1
npm install memdown@1.4.1 pnpm add memdown@1.4.1 yarn add memdown@1.4.1
Runtime dependencies
- ltgt ~2.2.0
- inherits ~2.0.1
- immediate ^3.2.3
- safe-buffer ~5.1.1
- abstract-leveldown ~2.7.1
- functional-red-black-tree ^1.0.1
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.
- abstract-leveldown@2.7.2 — direct
- functional-red-black-tree@1.0.1 — direct
- immediate@3.3.0 — direct
- inherits@2.0.4 — direct
- ltgt@2.2.1 — direct
- safe-buffer@5.1.2 — direct
- xtend@4.0.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.
| Code-Review | 0/10 — Found 1/23 approved changesets -- score normalized to 0 |
|---|---|
| Maintained | 0/10 — project is archived |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Security-Policy | 0/10 — security policy file not detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/memdown/1.4.1 — retrieved 2026-10-30T06:03:24.737Z
- https://api.deps.dev/v3/projects/github.com%2FLevel%2Fmemdown — retrieved 2026-10-30T00:56:14.380Z
- https://api.deps.dev/v3/systems/npm/packages/memdown/versions/1.4.1 — retrieved 2026-10-30T06:03:25.227Z
- https://api.deps.dev/v3/systems/npm/packages/memdown/versions/1.4.1:dependencies — retrieved 2026-10-30T06:03:25.254Z