Track Page view count and last visited timestamp
68%
Total Score
63
100
94
80
Only one registry publishing account is listed. Because the repository is owned by the same individual, this reflects a genuine single-maintainer capacity risk rather than merely a short organizational publishing list.
The registry namespace and repository owner are the same individual, and the repository is user-owned rather than organization-backed. This is coherent ownership but offers less institutional continuity than organization backing.
The repository recorded zero commits and zero active maintainers in the last three months. This is the clearest current maintenance concern, although the recent release and push provide some compensating evidence.
Composer build tooling is present, but no security-scanning tool was detected. The missing scanner is a transparency and process gap, not evidence that the package is unsafe.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This lowers transparency but is not by itself evidence of abandonment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
matomo/device-detector Version ^6.1 | — | — |
jaybizzle/crawler-detect Version ^1.2 | — | — |
getkirby/composer-installer Version ^1.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.