ajenbo/imap.php

MIT licensing, a clear README, and a minimal runtime dependency make the package easy to inspect and integrate. However, it has no tests or security policy, and the repository has seen no commits for about 8 years, limiting confidence in fixes and ongoing support.

Latest 0.9.3

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published about 8 years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency that may need compatibility or security fixes.

Repo commit activity

There were no commits and no active maintainers in the last 3 months, consistent with the long period since the last release. This materially lowers confidence in ongoing maintenance.

Project backing

The repository is owned by an individual rather than an organization, and the available project evidence shows no active maintenance to compensate for that limited backing.

Repo tooling

Composer is used for builds, but no security scanning tools are present. That is a meaningful security-maintenance gap, though it does not by itself make the package unfit.

Security policy

The repository has no security policy, leaving no documented path for reporting or handling vulnerabilities. This matters more for an IMAP client that handles mailbox authentication and mail data.