The repository matches the package, has a clear MIT license, and was pushed in July 2024. Its last registry release was in October 2017, while recent commit activity and security tooling are absent, leaving maintenance evidence thin.
52%
Total Score
67
100
81
83
The package has had no registry release since October 2017, despite being about 11 years old. This long release gap is a meaningful maintenance concern, although the repository was pushed in July 2024.
The repository is owned by the same individual represented by the registry namespace, rather than an organization. That gives clear ownership but provides no organizational maintenance capacity.
There were no commits and no active maintainers in the last three months. This weakens the reassurance from the July 2024 push and indicates limited current maintenance capacity.
Composer build tooling is present, but no security scanning tools were detected. For a small package this is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy. This reduces transparency about vulnerability reporting and handling, though it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
php-imap/php-imap Version ~2.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.