Package Health/xkerman/restricted-unserialize

xkerman/restricted-unserialize

The package is clearly licensed, has tests, and keeps runtime dependencies minimal. Its small audience, absent security policy, and lack of recent release or issue activity leave maintenance uncertainty.

Latest 1.1.12

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was about seven years ago, despite 20 releases overall and a previously regular cadence. No releases appeared in the last 12 months, which materially raises abandonment and compatibility risk.

Repo commit activity

The repository had no commits and no active maintainers in the last three months. The repository was pushed about three years ago, so maintenance appears to have largely stopped.

Repo issue activity

There were three open issues and three open pull requests, with no issues or pull requests opened or merged in the last month. This suggests limited recent project responsiveness.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. That weakens evidence that security-sensitive changes receive automated checking.

Security policy

The repository has no security policy. For a package focused on safely handling serialized input, this is a meaningful transparency and vulnerability-reporting gap.