object-extended 0.0.5
Additional object extensions with a chainable api
object-extended@0.0.5 was published on 2013-04-16. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All object-extended versions · Permanent reference to 0.0.5 · Latest release
Package specifications
| Version | 0.0.5 |
|---|---|
| License declaration | MIT |
| Published | 2013-04-16T16:14:33.636Z |
| Node.js requirement | Not declared |
| 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 | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 5 |
| Repository stars | 1 |
| Repository forks | 0 |
Install object-extended 0.0.5
npm install object-extended@0.0.5 pnpm add object-extended@0.0.5 yarn add object-extended@0.0.5
Runtime dependencies
- extended ~0.0.3
- is-extended ~0.0.3
- array-extended 0.0.4
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-extended@0.0.4 — direct
- declare.js@0.0.8 — indirect
- extended@0.0.6 — direct
- extender@0.0.10 — indirect
- is-extended@0.0.10 — 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 0/11 approved changesets -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — project is archived |
| SAST | 0/10 — no SAST tool detected |
| 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 |
Evidence and freshness
- https://registry.npmjs.org/object-extended/0.0.5 — retrieved 2026-10-30T07:39:18.502Z
- https://api.deps.dev/v3/projects/github.com%2Fdoug-martin%2Fobject-extended — retrieved 2026-10-30T07:04:21.259Z
- https://api.deps.dev/v3/systems/npm/packages/object-extended/versions/0.0.5 — retrieved 2026-10-30T07:39:19.018Z
- https://api.deps.dev/v3/systems/npm/packages/object-extended/versions/0.0.5:dependencies — retrieved 2026-10-30T07:39:19.037Z