Documentation, tests, release notes, and licensing make the package straightforward to adopt and maintain. Recent commits and organizational ownership help, but maintenance is concentrated in one contributor and workflow references are mostly unpinned.
68%
Total Score
67
100
94
67
Only one contributor made all three commits in the last 3 months, giving the project a concentrated recent maintenance base. Organization ownership provides some handoff capacity, but no second active contributor is shown.
Three commits were made in the last 3 months, indicating recent but limited maintenance activity. The low volume warrants some caution for a core library dependency.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest repository hygiene gap rather than evidence of abandonment.
The repository has no security policy. This reduces transparency about vulnerability reporting and response expectations, although it is not a direct indication that the package is unsafe.
Both workflows were analyzed successfully with no dangerous triggers, untrusted checkouts, script injection, or audit findings; one workflow scopes permissions at job level. However, 6 of 7 action references are unpinned, leaving avoidable build reproducibility and dependency-integrity risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
horde/mime Version ^3 || dev-FRAMEWORK_6_0 | — | — |
horde/util Version ^3 || dev-FRAMEWORK_6_0 | — | — |
horde/exception Version ^3 || dev-FRAMEWORK_6_0 | — | — |
horde/translation Version ^3 || dev-FRAMEWORK_6_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.