child_process 1.0.2

This package name is not currently in use, but was formerly occupied by another package. To avoid malicious use, npm is hanging on to the package name, but loosely, and we'll probably give it to you if you want it.

child_process@1.0.2 was published on 2016-08-26. Its manifest declares 0 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 child_process versions · Permanent reference to 1.0.2 · Latest release

Package specifications

Version1.0.2
License declarationISC
Published2016-08-26T02:04:55.033Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars164
Repository forks60

Install child_process 1.0.2

npm install child_process@1.0.2
pnpm add child_process@1.0.2
yarn add child_process@1.0.2

Runtime dependencies

  • None declared

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.

    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.

    Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
    Binary-Artifacts10/10 — no binaries found in the repo
    Code-Review5/10 — Found 3/6 approved changesets -- score normalized to 5
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Fuzzing0/10 — project is not fuzzed
    License0/10 — license file not detected
    SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
    Branch-Protection0/10 — branch protection not enabled on development/release branches
    Security-Policy0/10 — security policy file not detected

    Evidence and freshness