collection-map 1.0.0
Returns an array of mapped values from an array or object.
collection-map@1.0.0 was published on 2017-03-02. Its manifest declares 3 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 collection-map versions · Permanent reference to 1.0.0 · Latest release
Package specifications
| Version | 1.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2017-03-02T13:51:43.378Z |
| Node.js requirement | >=0.10.0 |
| 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 | 16 |
| Repository forks | 2 |
Install collection-map 1.0.0
npm install collection-map@1.0.0 pnpm add collection-map@1.0.0 yarn add collection-map@1.0.0
Runtime dependencies
- arr-map ^2.0.2
- for-own ^1.0.0
- make-iterator ^1.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.
- arr-map@2.0.2 — direct
- for-in@1.0.2 — indirect
- for-own@1.0.0 — direct
- kind-of@6.0.3 — indirect
- make-iterator@1.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.
| Code-Review | 0/10 — Found 0/3 approved changesets -- score normalized to 0 |
|---|---|
| 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 |
| 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/collection-map/1.0.0 — retrieved 2026-10-29T10:30:53.565Z
- https://api.deps.dev/v3/systems/npm/packages/collection-map/versions/1.0.0 — retrieved 2026-10-29T10:30:54.089Z
- https://api.deps.dev/v3/systems/npm/packages/collection-map/versions/1.0.0:dependencies — retrieved 2026-10-29T10:30:54.146Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fcollection-map — retrieved 2026-10-29T10:30:54.782Z