object.defaults
Like `extend` but only copies missing properties/values to the target object.
object.defaults@1.1.0 was published on 2017-04-26. Its manifest declares 4 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.
All object.defaults versions · Permanent reference to 1.1.0
Package specifications
| Version | 1.1.0 |
|---|---|
| License declaration | MIT |
| Published | 2017-04-26T18:26:00.510Z |
| Node.js requirement | >=0.10.0 |
| Type declarations | Not declared |
| Runtime dependency count | 4 |
| 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 | 0 |
| Resolved graph dependencies | 5 |
| Repository stars | 17 |
| Repository forks | 1 |
Install object.defaults 1.1.0
npm install object.defaults@1.1.0 pnpm add object.defaults@1.1.0 yarn add object.defaults@1.1.0
Runtime dependencies
- array-each ^1.0.1
- array-slice ^1.0.0
- for-own ^1.0.0
- isobject ^3.0.0
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.
- array-each@1.0.1 — direct
- array-slice@1.1.0 — direct
- for-in@1.0.2 — indirect
- for-own@1.0.0 — direct
- isobject@3.0.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.
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 | 1/10 — Found 2/20 approved changesets -- score normalized to 1 |
| 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/object.defaults/1.1.0 — retrieved 2026-10-29T10:55:01.187Z
- https://api.deps.dev/v3/systems/npm/packages/object.defaults/versions/1.1.0 — retrieved 2026-10-29T10:55:01.717Z
- https://api.deps.dev/v3/systems/npm/packages/object.defaults/versions/1.1.0:dependencies — retrieved 2026-10-29T10:55:01.749Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fobject.defaults — retrieved 2026-10-29T10:55:01.876Z