Browser detection library
70%
Total Score
67
100
94
75
All 2 recent commits came from one contributor, leaving recent maintenance concentrated in a single person; organization backing partly reduces handoff risk but does not remove it.
Only 2 commits occurred in the last 3 months, indicating limited recent development activity even though releases remain regular.
Composer build tooling is present, but no security scanning tools were detected, leaving a project-level assurance gap.
The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
All three workflows were analyzed with no high-confidence findings or dangerous triggers, but 8 of 10 action references are unpinned, which weakens build reproducibility.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
horde/http Version * || 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.