The stable version, GPL-2.0 declaration, and organization-backed repository provide useful baseline transparency. However, the project has not released or committed changes for over six years, has no security policy, and the repository does not clearly mention this package.
42%
Total Score
50
100
67
50
Only two releases exist, with the latest published over seven years ago and none in the last 12 months. This is strong evidence that maintenance has stopped or substantially slowed.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long release gap and raising abandonment risk.
The package has no README, while tests and a changelog are absent; tests and changelogs are normal to omit from published artifacts, but the missing consumer-facing README modestly reduces transparency for this extension.
The repository name does not match the package name, and no README mention was found. That makes package ownership and source-to-artifact traceability less clear, although the repository otherwise contains a matching-looking extension tree.
The linked repository has no security policy. For an unmaintained package, this leaves vulnerability reporting and response expectations unclear.
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.