react-immutable-pure-component 1.2.3

React PureComponent implementation embracing Immutable.js

react-immutable-pure-component@1.2.3 was published on 2018-08-03. Its manifest declares 1 runtime dependency and 3 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All react-immutable-pure-component versions · Permanent reference to 1.2.3 · Latest release

Package specifications

Version1.2.3
License declarationMIT
Published2018-08-03T12:31:58.946Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count3
Optional dependency count1
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size15.12 KiB
Published file count7
Package typeNot declared
ES module entrylib/react-immutable-pure-component.es.js
Default entrylib/react-immutable-pure-component.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies2
Repository stars30
Repository forks2

Install react-immutable-pure-component 1.2.3

npm install react-immutable-pure-component@1.2.3
pnpm add react-immutable-pure-component@1.2.3
yarn add react-immutable-pure-component@1.2.3

Runtime dependencies

Peer requirements

Optional dependencies

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
Code-Review0/10 — Found 0/27 approved changesets -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness