shrink0r/monatic

Usable with caveats: the package is licensed, documented, tested, and backed by a matching repository, but its latest release was more than six years ago and current repository activity is absent. The small project footprint and lack of a security policy add maintenance risk.

Latest 0.2.2

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were no commits and no active maintainers in the measured three-month period. Combined with no recent releases, this indicates current maintenance has effectively stalled.

Project backing

The registry namespace and repository owner match, and both are associated with the same individual account. This provides direct ownership continuity, though it does not offer the redundancy of organization backing.

Release history

Only four releases are recorded, with none in the last 12 months and the latest published more than six years ago. This is a meaningful maintenance concern for a library, despite the repository having been pushed more recently.

Repo popularity

The repository has 24 stars, one fork, and five watchers, indicating a small user and contributor footprint. Popularity is only supporting evidence, but the limited footprint provides little resilience if the maintainer stops responding.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap, though it is less severe because the repository has no automated workflows to expose tokens or execute untrusted code.