The package includes a README and changelog, and its single runtime dependency is explicit. Its source has had no commits since January 2016, with no recent issue or pull-request activity, and the repository does not clearly identify this package.
38%
Total Score
25
75
75
This is the package's only release, published in January 2016, with no releases in the last 12 months. The long period without a new release is a substantial maintenance and abandonment concern.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package having received no release since January 2016. This strongly indicates an inactive project.
There were no new or closed issues or pull requests in the last month. This is not harmful alone, but alongside the absent commit activity it provides no evidence of ongoing maintenance.
The repository name does not match the package name and its README does not mention the package. Although name differences can occur for subpackages, the lack of any README reference leaves the source relationship unclear.
The linked repository has no security policy. For an old package with no recent development activity, this adds a transparency gap and provides no documented channel for handling vulnerabilities.
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.