Organization ownership and a small dependency set offer some continuity, while the repository is not archived. There is no security policy or automated security scanning, so future maintenance and transparency remain limited.
42%
Total Score
75
100
69
75
This is the package's only release, published about seven years ago, with no releases in the last 12 months. That strongly suggests abandonment risk for a dependency.
No license is declared, no license file is present in the package, and no repository license file was found. That leaves the legal terms for reuse unclear.
The package has no README, tests, or changelog. Missing tests and changelog are normal for a published theme artifact, but the absent README slightly reduces consumer guidance.
There were no commits and no active maintainers in the last three months. Combined with the single historical release, this supports a substantial abandonment concern.
Composer is used as a build tool, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version ~1.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.