react-immutable-proptypes

Release historydanger

The project has 26 releases and a historically active cadence, but its latest release was about six years ago and there were no releases in the last year. That long pause materially raises abandonment and compatibility risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old latest release, this is the strongest evidence of stalled maintenance.

Build provenancecaution

No build attestation or trusted-publisher identity is provided, reducing publication transparency. This is a supply-chain hygiene gap, but not by itself evidence that the release is unfit.

Lifecycle scriptscaution

A prepublish lifecycle script is present, adding some build or publication complexity compared with a package without install-related scripts, though it is not itself evidence of an unsafe release.

Project backingcaution

The repository is owned by an individual rather than an organization, so there is no organizational backing signal to offset the thin maintenance picture.