laiz/laiz-monad

Tests, documentation, an MIT license, and a small dependency footprint make the package straightforward to inspect. Its single-maintainer setup and lack of security policy add little resilience.

Latest v0.3.2

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no releases in over ten years, and none in the last 12 months. Its earlier 11-release history shows it was once active but does not offset the current abandonment risk.

Repo commit activity

There were no commits or active maintainers in the last three months, consistent with the repository having stopped changing in 2016. This is strong evidence of abandonment risk for a dependency.

Maintainers

Only one registry account has publish access, limiting publishing resilience, although this administrative count does not prove that the project lacks other contributors.

Project backing

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

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is consistent with an inactive project, though the absence of open work alone is not severe.