Documentation, a changelog, and release notes are present, while the single runtime dependency keeps integration relatively simple. The repository remains available and organizationally backed, but these positives do not offset the lack of recent project activity.
43%
Total Score
50
75
50
The package has had only two releases, both in March 2017, with no releases in over 9 years. Its stable version and documented release notes provide some context, but the prolonged absence of releases is a substantial abandonment concern.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the package's long release gap. The repository is not archived, but there is no observed recent maintenance to compensate.
There were no new or closed issues or pull requests in the last month, and no pull requests were merged. This reinforces the lack of recent activity, although the null open-issue count limits what can be concluded about unresolved demand.
Composer build tooling is present, but no security-scanning tooling is reported. This is a hygiene gap rather than evidence of a vulnerability, and the package's clear source tree partly improves transparency.
The repository has no security policy. For an old package that handles uploaded files and email attachments, this reduces transparency around vulnerability reporting and maintenance responsibility.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ezsystems/ezpublish-legacy-installer Version * | — | — |
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.