memcpy
Copies data between node Buffers and/or ArrayBuffers up to ~75 times faster than in pure JS.
memcpy@0.6.0 was published on 2015-07-14. 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.8 <=0.12.
All memcpy versions · Permanent reference to 0.6.0
Package specifications
| Version | 0.6.0 |
|---|---|
| License declaration | Apache-2.0 |
| Published | 2015-07-14T21:16:57.099Z |
| Node.js requirement | >=0.8 <=0.12 |
| 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 | src/memcpy.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | 54 |
| Repository forks | 9 |
Install memcpy 0.6.0
npm install memcpy@0.6.0 pnpm add memcpy@0.6.0 yarn add memcpy@0.6.0
Runtime dependencies
- bindings ~1.1
- nan ~1.2.0
- node-arraybuffer ^1.0.11
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.
- bindings@1.1.1 — direct
- nan@1.2.0 — direct
- node-arraybuffer@1.0.12 — 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 | 0/10 — Found 1/18 approved changesets -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — project is archived |
| 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 |
| 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/memcpy/0.6.0 — retrieved 2026-10-29T12:14:41.260Z
- https://api.deps.dev/v3/systems/npm/packages/memcpy/versions/0.6.0 — retrieved 2026-10-29T12:14:41.815Z
- https://api.deps.dev/v3/systems/npm/packages/memcpy/versions/0.6.0:dependencies — retrieved 2026-10-29T12:14:41.822Z
- https://api.deps.dev/v3/projects/github.com%2FdcodeIO%2Fnode-memcpy — retrieved 2026-10-29T12:14:41.945Z