Risky to adopt: the last release was in November 2017 and the repository has had no recent commits or issue resolution. Good documentation, tests, licensing, and a non-archived, non-deprecated project reduce—but do not remove—the abandonment risk.
45%
Total Score
25
79
83
The latest release was in November 2017, with no releases in the last 12 months despite a package history of nine releases. This long period without a release is a substantial maintenance and compatibility concern.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap. This is strong evidence of inactive maintenance.
There were no new or closed issues or pull requests in the last month, while three issues and one pull request remain open. This suggests little current project attention.
Composer is used as the build tool, but no security scanning tools are present. The missing scanning is a modest transparency and maintenance gap, not evidence that the package is unsafe by itself.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap for a library that handles email composition and transport.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
zendframework/zend-mail Version ^2.2.1 | — | — |
zendframework/zend-view Version ^2.2.1 | — | — |
zendframework/zend-filter Version ^2.2.1 | — | — |
zendframework/zend-escaper Version ^2.2.1 | — | — |
zendframework/zend-validator Version ^2.2.1 | — | — |
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.