A stable version, release notes, repository tests, and a matching GPL-2.0 license improve transparency. Composer-only tooling and no security policy leave limited assurance for this legacy integration.
15%
Total Score
50
100
50
75
Packagist marks the entire package as abandoned, with no replacement specified. This is a severe maintenance and adoption risk for a new dependency.
The package has only two releases, both from June 2017, and none in the last 12 months. Its roughly nine-year-old release history indicates substantial abandonment risk.
There were no commits and no active maintainers in the last three months, consistent with the archived repository and abandoned registry status.
The linked repository is archived and was last pushed in April 2018, so the source is no longer actively maintained.
The repository name does not match the package name and its README does not mention the package. Although the organization context reduces the chance of a mistaken repository, this remains a transparency concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ezsystems/legacy-bridge Version ^1.2 | — | — |
ezsystems/ezpublish-kernel Version ^6.0 | — | — |
ezsystems/ezplatform-xmltext-fieldtype Version ^1.2 | — | — |
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.