o2system/email

The package is small, clearly licensed, and has a focused file tree with no install-time scripts. Its last release and repository activity were about six years ago, while both workflow actions are unpinned and no security policy or scanning is present.

Latest v2.0.20

Packagist

42%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was about six years ago, with no releases in the last 12 months. Although the package had 14 releases and a previously regular cadence, the long current gap is a substantial abandonment concern.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with activity having stopped about six years ago. This materially increases the risk that defects and compatibility changes will go unaddressed.

Repo popularity

The repository has zero stars and forks and only two watchers, offering little supporting evidence of community adoption. Popularity is secondary, but it does not offset the maintenance gap.

Repo tooling

Composer is used for the build, but no security-scanning tools are configured. For a library that sends email and depends on several runtime packages, this is a meaningful security-hygiene gap.

Security policy

The repository has no security policy, leaving no documented path for reporting vulnerabilities. This adds a transparency gap, especially alongside the lack of recent maintenance.