frootbox/mail

Clear licensing, documentation, and a recent release provide useful transparency. The small project has no tests or security scanning, so pinning this pre-1.0 dependency deserves care.

Latest 0.2

Packagist

69%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The package includes a substantial README and a changelog, which help consumers understand and track it. No tests are published or present in the repository, a minor maintenance gap for a mail library.

Repo commit activity

There were no commits and no active maintainers in the three months before collection. The recent push and release history partly offset this, but the current development lull is a real maintenance concern.

Repo popularity

The repository has zero stars, forks, and watchers, indicating little visible external adoption or review. Popularity is only supporting evidence, so this lowers confidence more than it determines the health verdict.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured. For a package handling mail credentials and transport, that leaves a meaningful security-maintenance gap.

Security policy

The repository has no security policy. This reduces transparency for reporting vulnerabilities in a package that handles SMTP configuration and message delivery.