yasser-elgammal/green

This is a healthy, actively maintained release with strong package transparency: it is MIT-licensed, has a substantial README, tests, changelog, documentation, and a coherent 158-file application skeleton. The package has released 22 versions over 157 days, with the latest release published recently and a stable, non-prerelease version. The repository is active, unarchived, matches the package, and has recent pull-request merges. The main risks are that all 17 commits in the last 3 months came from one contributor, the repository has no security policy or security-scanning tooling, and the project remains relatively small with 23 stars and one fork. It appears reasonable to depend on, but users should account for the single-maintainer bus factor and independently review updates.

Latest v2.6.0

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account, Yasser Elgammal, has publish access. This is consistent with the repository being user-owned, but it creates limited publishing redundancy.

Project backing

The repository is owned by a GitHub user rather than an organization, so the single-maintainer and single-publisher concentration is not compensated by visible organizational backing.

Repo bus factor

One contributor made all 17 commits in the last 3 months, creating a clear single-maintainer continuity risk for this user-owned project.

Repo commit activity

The repository recorded 17 commits in the last 3 months, showing recent activity, but all activity came from one active maintainer.

Repo tooling

Composer is used as a build tool, but no security-scanning tools are configured. The missing scanning coverage is a hygiene gap, though it is not evidence of malicious behavior by itself.