The proprietary license and repository/package mismatch add adoption concerns. A README, broad test suite, and organizational ownership provide useful context, but do not establish ongoing support.
42%
Total Score
50
58
75
This is the package's only release, published nearly eight years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk.
The release declares a proprietary license and has no detected license file. It is therefore licensed as declared, but the proprietary terms may restrict ordinary open-source use.
There are no open issues or pull requests and no issue or pull-request activity in the last month. This is consistent with a project that is no longer actively maintained.
The linked repository name does not match the package name and its README does not mention the package. Although this could reflect a wrapper or organization structure, the ownership relationship is not clearly established.
Composer is used for the build, but no security scanning tooling is present. This is a modest maintenance-hygiene gap rather than a severe dependency risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
linkorb/etcd-php Version ^1.5 | — | — |
guzzlehttp/guzzle Version ^6.3 | — | — |
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.