The source repository is still available and matches the package, with a clear license, tests, README, and release notes. Maintenance has nevertheless gone quiet, and the repository lacks security scanning and a security policy.
58%
Total Score
50
100
88
75
The package and repository are owned by the same individual account, so the source ownership is consistent, but there is no organization backing shown to compensate for the thin maintenance base.
The package has 10 releases since January 2015, but none in the last 12 months and its latest registry release was in December 2019. This is a meaningful maintenance concern despite its established release history.
There were no commits and no active maintainers in the most recent three-month window. Combined with the old registry release, this raises abandonment and compatibility risk.
The repository has 48 open issues and 5 open pull requests, but no issues or pull requests were opened or closed in the last month. This supports the concern that maintenance is currently inactive.
Composer build tooling is present, but no security scanning tools were detected. That is a hygiene gap, though it is not severe enough to make the release unfit by itself.
| Title | Versions | Severity |
|---|---|---|
CVE-2018-19246 athlon1600/php-proxy is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor in versions 0.0.0 - 5.1.0. | 0.0.0 - 5.1.0 | High |
CVE-2018-19784 athlon1600/php-proxy is vulnerable to Inadequate Encryption Strength in versions 0.0.0 - 5.1.0. | 0.0.0 - 5.1.0 | High |
No maintainer information available.
No direct dependencies.
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.