Strong tests, release notes, licensing, and organization backing improve confidence for consumers. Workflow references are mostly unpinned, and security scanning is not present, but neither is paired with a more serious workflow finding.
82%
Total Score
83
100
94
75
All five recent commits came from one contributor, creating a real concentration risk; organization backing partly reduces handoff risk but does not remove it.
Composer build tooling is present, but no security-scanning tool was detected, leaving a modest transparency and maintenance gap.
The repository has no security policy, which weakens vulnerability-reporting transparency for a library consumed by other projects.
Both workflows were analyzed without dangerous triggers or audit findings, and one scopes permissions at job level; however, 6 of 7 action references are unpinned, which is a workflow hygiene caution.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
horde/util Version ^3 || dev-FRAMEWORK_6_0 | — | — |
horde/support Version ^3 || dev-FRAMEWORK_6_0 | — | — |
horde/exception Version ^3 || dev-FRAMEWORK_6_0 | — | — |
psr/http-message Version ^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.