The package includes tests, a usable README, and a small runtime dependency surface. Its single-person publishing base and absent security policy or scanning reduce confidence in long-term maintenance.
58%
Total Score
50
100
83
75
Only one account has registry publishing access. That is a thin publishing base for continuity, although registry access alone does not establish who actively maintains the code.
The package has five releases over roughly four and a half years, but none in the last 12 months; the latest release was over a year ago. This indicates slowed maintenance despite a previously established release history.
The repository recorded zero commits and zero active maintainers in the last three months. The repository is not archived, but this recent inactivity weakens evidence of ongoing maintenance.
Composer is used for the build, but no security scanning tools are present. This is a maintenance and hygiene gap, though it is not evidence of a security defect by itself.
The repository has no security policy. For a library handling client and server transport, this reduces transparency around vulnerability reporting and response.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
apache/thrift Version ^0.21.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.