It has a README and matches its repository, but the project has no security policy or automated security scanning. One publisher and a single runtime dependency provide limited additional assurance.
32%
Total Score
75
79
50
Neither the package metadata nor the artifact or repository contains a license, leaving the legal terms for using this dependency unclear.
The package has made no release in nearly 10 years: its latest release was in October 2016, with no releases in the last 12 months. This is strong evidence of abandonment despite the package remaining undepricated.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and providing no evidence of current maintenance.
Composer build tooling is present, but no security-scanning tools are configured. That leaves dependency and source-risk checks less visible than they would be in an actively maintained project.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This adds a transparency gap for a package that interacts with Docker environments.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
omauger/docker-compose-php Version @dev | — | — |
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.