The package includes a usable README, a documented exact-version release, and a declared MIT license. Its source project has no security policy or scanning, while the repository appears unrelated to the package, making ongoing support and provenance harder to trust.
43%
Total Score
50
50
50
The latest release was about two years and five months ago, with no releases in the last 12 months and only three releases overall. This is strong evidence of stalled maintenance for a theme package.
The repository name does not match the package, and its README does not mention the package. That weakens confidence that the linked source actually corresponds to this release.
The linked repository recorded no commits and no active maintainers in the last three months, which reinforces the long release gap and raises abandonment risk.
The project uses Composer, but no security scanning tools were detected. For a package containing executable PHP and frontend assets, that leaves a meaningful maintenance and review gap.
The repository has no security policy. This is a transparency and response-process gap, although it does not by itself show that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
jenssegers/agent Version ^2.6 | — | — |
laravel/framework Version ^6|^7|^8 | — | — |
hacoidev/ophim-core Version ^1.0.0 | — | — |
ckfinder/ckfinder-laravel-package Version v3.5.2.1 | — | — |
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.