object-tools 1.6.4
Useful functions for working with objects
object-tools@1.6.4 was published on 2015-05-19. Its manifest declares 2 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.
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
All object-tools versions · Permanent reference to 1.6.4 · Latest release
Package specifications
| Version | 1.6.4 |
|---|---|
| License declaration | MIT |
| Published | 2015-05-19T14:09:00.530Z |
| Node.js requirement | Not declared |
| 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 | ./lib/object-tools.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | 1 |
| Repository forks | 2 |
Install object-tools 1.6.4
npm install object-tools@1.6.4 pnpm add object-tools@1.6.4 yarn add object-tools@1.6.4
Runtime dependencies
- typical ^2.2
- array-tools ^1.1.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-tools@1.8.6 — direct
- object-tools@1.6.7 — indirect
- typical@2.6.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 — project is archived |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Code-Review | 0/10 — Found 2/30 approved changesets -- score normalized to 0 |
| 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-tools/1.6.4 — retrieved 2026-10-29T14:23:57.614Z
- https://api.deps.dev/v3/projects/github.com%2F75lb%2Fobject-tools — retrieved 2026-10-29T13:38:29.726Z
- https://api.deps.dev/v3/systems/npm/packages/object-tools/versions/1.6.4 — retrieved 2026-10-29T14:23:58.123Z
- https://api.deps.dev/v3/systems/npm/packages/object-tools/versions/1.6.4:dependencies — retrieved 2026-10-29T14:23:58.149Z