array-tools 1.4.2
Useful functions for working with arrays
array-tools@1.4.2 was published on 2015-02-01. 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 array-tools versions · Permanent reference to 1.4.2 · Latest release
Package specifications
| Version | 1.4.2 |
|---|---|
| License declaration | MIT |
| Published | 2015-02-01T12:25:14.035Z |
| 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/array-tools.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 5 |
| Repository stars | 9 |
| Repository forks | 3 |
Install array-tools 1.4.2
npm install array-tools@1.4.2 pnpm add array-tools@1.4.2 yarn add array-tools@1.4.2
Runtime dependencies
- typical ^1.0.0
- object-tools ^1.1.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.
- object-tools@1.6.7 — direct
- typical@1.0.0 — direct
- array-tools@1.8.6 — indirect
- typical@2.6.1 — indirect
- typical@2.6.1 — indirect
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 1/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/array-tools/1.4.2 — retrieved 2026-10-29T21:39:07.708Z
- https://api.deps.dev/v3/projects/github.com%2F75lb%2Farray-tools — retrieved 2026-10-29T21:25:54.338Z
- https://api.deps.dev/v3/systems/npm/packages/array-tools/versions/1.4.2 — retrieved 2026-10-29T21:39:08.267Z
- https://api.deps.dev/v3/systems/npm/packages/array-tools/versions/1.4.2:dependencies — retrieved 2026-10-29T21:39:08.297Z