assign-deep
Deeply assign the values of all enumerable-own-properties and symbols from one or more source objects to a target object. Returns the target object.
assign-deep@1.0.1 was published on 2019-06-19. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=6.
All assign-deep versions · Permanent reference to 1.0.1
Package specifications
| Version | 1.0.1 |
|---|---|
| License declaration | MIT |
| Published | 2019-06-19T17:53:52.381Z |
| Node.js requirement | >=6 |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 9.66 KiB |
| Published file count | 4 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 1 |
| Repository stars | 78 |
| Repository forks | 13 |
Install assign-deep 1.0.1
npm install assign-deep@1.0.1 pnpm add assign-deep@1.0.1 yarn add assign-deep@1.0.1
Runtime dependencies
- assign-symbols ^2.0.2
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.
- assign-symbols@2.0.2 — 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.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Code-Review | 0/10 — Found 0/29 approved changesets -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| 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 |
| 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 |
| Security-Policy | 0/10 — security policy file not detected |
Evidence and freshness
- https://registry.npmjs.org/assign-deep/1.0.1 — retrieved 2026-10-29T22:47:59.976Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fassign-deep — retrieved 2026-10-29T22:48:00.523Z
- https://api.deps.dev/v3/systems/npm/packages/assign-deep/versions/1.0.1 — retrieved 2026-10-29T22:58:08.311Z
- https://api.deps.dev/v3/systems/npm/packages/assign-deep/versions/1.0.1:dependencies — retrieved 2026-10-29T22:58:08.336Z