lemmon/id

Documentation is strong, and the dependency surface is small. Maintenance currently rests on one contributor, while all eight workflow actions are unpinned; pinning them and broadening ownership would reduce adoption risk.

Latest v0.2.1

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The registry namespace and repository are owned by the same individual account, confirming direct ownership but not organizational backing or a handoff path.

Repo bus factor

One contributor made 100% of the four commits in the last three months. The repository is user-owned rather than organization-owned, so there is no provided project-backing signal to offset this concentration.

Repo commit activity

Four commits were made in the last three months, including activity on the assessment date, so maintenance has not stopped. All observed activity comes from one maintainer, limiting resilience.

Repo tooling

Composer build tooling is present, but no security scanning tool was detected. For a small library this is a modest transparency and maintenance gap, not a severe risk by itself.

Security policy

The repository has no security policy. This weakens the documented process for reporting and handling vulnerabilities, although the package's small scope and other maintenance evidence partly limit the concern.