milirezai/milirulepilot

Its README, MIT declaration, small dependency surface, and lack of install-time scripts make adoption straightforward. The project is young, so longer-term resilience remains unproven.

Latest v1.2.10

Packagist

65%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact includes a substantial README, and the repository uses GitHub Releases, but it has no tests or changelog. Missing tests reduce confidence for a business-rules library, while the absent changelog is not a packaging gap.

Project backing

The repository is owned by the same individual as the registry namespace, and the owner type is User rather than Organization. This confirms direct ownership but provides no organizational maintenance redundancy.

Repo bus factor

One contributor made all 13 commits in the last 3 months, giving the project a single-maintainer bus factor. That concentration creates a meaningful continuity risk for a young library.

Repo tooling

Composer is used as the build tool, but no security-scanning tool is configured. The build setup is appropriate, while the missing scanning coverage is a modest transparency gap.

Security policy

The repository has no security policy. For a business-rules library this is a transparency and incident-reporting gap, although it is not by itself evidence of unsafe code.