phpdot/mail

phpdot/mail appears usable and reasonably transparent, with an MIT license, a coherent package and repository file layout, repository-level unit and integration tests, recent repository activity, and organization ownership. However, it is a young v0.x package only 53 days old with three releases, all recent commits come from one contributor, and the repository has neither security scanning nor a published security policy. These are meaningful maturity and maintenance-resilience concerns, but the active repository, organization backing, matching package repository, and testing evidence keep the release in the caution rather than unhealthy range.

Latest v0.3.0

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is only 53 days old with three releases and a median release interval of about 27 days. This is active early development, but it provides limited evidence of long-term maintenance and maturity.

Repo bus factor

One contributor made all three commits in the measured period, creating a concentrated maintenance dependency. Organization ownership provides some potential for handoff, but no second active contributor is shown.

Repo commit activity

There were three commits in the last three months and the repository was updated recently, indicating ongoing activity, though the volume is modest for establishing durable maintenance.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured. The missing scanning reduces supply-chain assurance, although it is not by itself evidence of an unsafe release.

Security policy

The repository has no published security policy, leaving vulnerability reporting and response expectations unclear.