Clear documentation and a complete test-backed source tree make integration easier. The organization-backed project is still releasing, though recent work is concentrated in one contributor and security-process coverage is limited.
79%
Total Score
67
100
94
83
One contributor made all recent commits, giving the project a 100% top-contributor share. Organization backing provides some handoff capacity, but the observed recent activity remains concentrated.
Only 2 commits were recorded in the last 3 months, so recent source activity is limited even though releases continue. This is a mild maintenance concern rather than evidence of abandonment.
Composer build tooling is present, but no security scanning tools were detected. The build path is established while automated security coverage is limited.
The repository has no security policy. For an authentication library, the absence of a documented vulnerability-reporting process is a meaningful transparency gap.
Both workflows were analyzed successfully with no reported audit findings, no untrusted checkouts, and no script injection. However, 2 of 4 action references are unpinned, which leaves some build reproducibility risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
horde/util Version ^3 || dev-FRAMEWORK_6_0 | — | — |
horde/exception Version ^3 || dev-FRAMEWORK_6_0 | — | — |
horde/translation Version ^3 || dev-FRAMEWORK_6_0 | — | — |
horde/horde-installer-plugin Version dev-FRAMEWORK_6_0 || ^3 || ^2 | — | — |
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.