The repository is not archived and the package has a clear license, README, tests, and stable version. No security policy leaves limited guidance for handling issues, while the project shows little recent activity.
42%
Total Score
50
100
81
88
The latest release was in April 2020, about six years ago, with no releases in the last 12 months. That long gap is a substantial abandonment concern despite the package having seven releases overall.
The repository recorded zero commits and zero active maintainers in the last three months. This indicates no current maintenance capacity for a dependency with an aging release.
There were no new or closed issues or pull requests in the last month, although three pull requests remain open. This supports the broader picture of limited current project activity.
The repository uses Composer and Phing for build tasks, showing some build structure. It has no security-scanning tools, which is a modest maintenance and transparency gap for an aging project.
The repository has no security policy or documented security-reporting process. The README points users to external documentation, but the repository itself provides no current guidance.
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.