Its stable version, clear README, and minimal dependency footprint reduce integration surprises. Maintenance has effectively stopped, and the repository’s weak package identity makes long-term support uncertain.
35%
Total Score
50
100
75
50
The package has had only two releases, with the latest published more than 10 years ago and none in the last 12 months. This is strong evidence of abandonment for a dependency expected to receive ongoing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no release since 2016. No provided signal compensates for this lack of recent maintenance.
The linked repository name does not match the package name and its README does not mention the package, weakening confidence that it is the package’s authoritative source. The organization backing helps somewhat, but does not resolve the identity gap.
The repository has no security policy or security-reporting guidance. This is a modest transparency gap, though the package’s small, legacy scope limits its weight relative to the clear maintenance concerns.
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.