@achrinza/node-ipc 10.1.2

A nodejs module for local and remote Inter Process Communication (IPC), Neural Networking, and able to facilitate machine learning.

@achrinza/node-ipc@10.1.2 was published on 2022-03-20. Its manifest declares 4 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is 14 || 16 || 17.

Deprecated: Contains nested transient production dependencies managed by @riaevangelist. Upgrade to `@achrinza/node-ipc@10.1.3` or higher.

All @achrinza/node-ipc versions · Permanent reference to 10.1.2 · Latest release

Package specifications

Version10.1.2
License declarationMIT
Published2022-03-20T08:32:43.228Z
Node.js requirement14 || 16 || 17
Type declarationsNot declared
Runtime dependency count4
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size131.31 KiB
Published file count23
Package typemodule
ES module entrynode-ipc.js
Default entrynode-ipc.cjs
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies49
Repository stars41
Repository forks13

Install @achrinza/node-ipc 10.1.2

npm install @achrinza/node-ipc@10.1.2
pnpm add @achrinza/node-ipc@10.1.2
yarn add @achrinza/node-ipc@10.1.2

Runtime dependencies

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
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies3/10 — dependency not pinned by hash detected -- score normalized to 3
Code-Review0/10 — Found 0/27 approved changesets -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts10/10 — no binaries found in the repo
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness