Its clear license, linked repository, and usable README provide basic transparency, but security coverage is thin and installation depends on several Composer scripts. Avoid it for new phpMyAdmin deployments unless you can maintain the project yourself.
32%
Total Score
50
75
50
The package has had only two releases, with the latest published in April 2017 and none in the last 12 months. That long release gap is strong evidence of abandonment for a deployment boilerplate.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the release history showing no activity for about nine years.
The package runs post-create, post-install, and post-update Composer scripts, adding maintenance and execution complexity to a project whose source activity has stopped.
The linked repository has no security policy. This is a transparency and maintenance gap, especially for a deployment-oriented package, though it does not by itself show unsafe behavior.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version ^1.2 | — | — |
phpmyadmin/phpmyadmin Version ^4.7 | — | — |
cweagans/composer-patches Version ^1.6 | — | — |
derhasi/composer-preserve-paths Version ^0.1 | — | — |
wikimedia/composer-merge-plugin Version ^1.4 | — | — |
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.