The package includes a changelog, a small dependency surface, and an active organization-owned repository. Its release history is stale, recent commit activity is absent, and the declared Apache license conflicts with the BSD license file; the workflow also leaves two of three actions unpinned.
52%
Total Score
75
100
79
75
The artifact includes a license file, but it identifies BSD-3-Clause while the manifest declares Apache 2.0. This mismatch creates avoidable uncertainty for adopters.
The package has had no release in over two years, with zero releases in the last 12 months. That is a meaningful maintenance concern despite four releases overall.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the stale registry release history, this points to limited current maintenance.
Composer is used for builds, but no security scanning tooling was detected. This is a hygiene gap rather than evidence that the package is unsafe or abandoned on its own.
The repository has no security policy, reducing transparency about vulnerability reporting. This is a moderate governance gap, partly offset by the organization-owned repository.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
horde/thrift Version * | — | — |
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.