A complete README, tests, changelog, MIT license, and release notes support practical adoption. The workflows use five unpinned actions, and no security policy or scanning tools were found; the single registry maintainer also limits visible resilience.
58%
Total Score
38
50
83
83
The repository recorded zero commits and zero active maintainers over the last three months. Combined with the release history, this indicates maintenance has effectively stopped.
The package has six runtime dependencies, including several detection libraries. This is a meaningful dependency surface but not excessive for a library that combines browser, device, crawler, and parser functionality.
One registry maintainer account is listed. That is a limited publishing base, and no organizational backing is shown to compensate for the concentration.
The repository is owned by an individual user rather than an organization. This does not make the package unhealthy by itself, but it provides no organizational backing to compensate for the thin maintainer base.
The package has only two releases, both published within about 1 day, and none in the last 12 months despite being about 2 years and 8 months old. This is strong evidence of stalled maintenance, although the stable release and complete project files provide some compensation.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
league/pipeline Version ^1.0 | — | — |
ua-parser/uap-php Version ~3.9 | — | — |
matomo/device-detector Version ^6.0 | — | — |
jaybizzle/crawler-detect Version ~1.2 | — | — |
mobiledetect/mobiledetectlib Version ~3.74 | — | — |
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.