The repository has had no commits or issue activity for over five years, and the project has only one registry maintainer. MIT licensing, a matching repository, documented usage, and a GitHub release provide useful transparency but do not offset the abandonment risk.
42%
Total Score
50
100
72
83
The package has 29 releases since February 2017, but none in the last 12 months and the latest release was over five years ago. This long release gap materially raises abandonment risk.
There were zero commits and zero active maintainers in the last three months, consistent with the repository's last push being over five years ago. This is the strongest maintenance concern.
Only one registry account has publish access. That is a narrow publishing base, although the organization-owned repository makes a short registry maintainer list less concerning than it would be for an individual project.
There is one open issue and one open pull request, but no issues or pull requests were created or closed in the last month. This supports the broader picture of inactivity.
The repository has only 1 star and 1 fork, indicating limited external adoption and a small community buffer if the maintainer stops responding.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
php-http/httplug Version ^1.0 | — | — |
php-http/discovery Version ^1.0 | — | — |
symfony/property-access Version ^3.0 || ^4.0 || ^5.0 | — | — |
php-http/message-factory Version ^1.0.2 | — | — |
php-http/multipart-stream-builder Version ^0.1 || ^0.2 || ^1.0 | — | — |
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.