nanoclone

300B to deep clone JavaScript objects

nanoclone@1.0.2 was published on 2023-05-11. 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 nanoclone versions · Permanent reference to 1.0.2

Package specifications

Version1.0.2
License declarationMIT
Published2023-05-11T01:22:06.548Z
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 size7.12 KiB
Published file count10
Package typeNot declared
ES module entrysrc/index.js
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars71
Repository forks10

Install nanoclone 1.0.2

npm install nanoclone@1.0.2
pnpm add nanoclone@1.0.2
yarn add nanoclone@1.0.2

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/24 approved changesets -- score normalized to 1
    Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
    Binary-Artifacts10/10 — no binaries found in the repo
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Security-Policy0/10 — security policy file not detected
    Fuzzing0/10 — project is not fuzzed
    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