mixin-deep 1.2.0
Deeply mix the properties of objects into the first object. Like merge-deep, but doesn't clone.
mixin-deep@1.2.0 was published on 2017-03-02. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.10.0.
Deprecated: Critical bug fixed in v2.0.1, please upgrade to the latest version.
All mixin-deep versions · Permanent reference to 1.2.0 · View npm registry JSON · Latest release
Package specifications
| Version | 1.2.0 |
|---|---|
| License declaration | MIT |
| Published | 2017-03-02T13:40:45.198Z |
| Node.js requirement | >=0.10.0 |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| 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 | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 2 |
| Resolved graph dependencies | 2 |
| Repository stars | 79 |
| Repository forks | 18 |
Install mixin-deep 1.2.0
npm install mixin-deep@1.2.0 pnpm add mixin-deep@1.2.0 yarn add mixin-deep@1.2.0
Runtime dependencies
- for-in ^1.0.2
- is-extendable ^0.1.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.
- for-in@1.0.2 — direct
- is-extendable@0.1.1 — 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.
Known direct advisories
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 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Code-Review | 0/10 — Found 0/30 approved changesets -- score normalized to 0 |
| SAST | 0/10 — no SAST tool detected |
| 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 |
Evidence and freshness
- Readable npm registry JSON — retrieved 2026-11-06T08:45:38.886Z
- https://api.deps.dev/v3/systems/npm/packages/mixin-deep/versions/1.2.0 — retrieved 2026-11-06T08:45:38.962Z
- https://api.deps.dev/v3/systems/npm/packages/mixin-deep/versions/1.2.0:dependencies — retrieved 2026-11-06T08:45:38.992Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fmixin-deep — retrieved 2026-11-06T05:41:02.474Z