The MIT license, README, and single runtime dependency make the package straightforward to inspect and adopt. Its only release is from October 2012, repository activity is sparse, and the linked repository does not identify the package; use only when you can accept legacy maintenance.
38%
Total Score
50
100
71
50
The package has only one release, published in October 2012, with no releases in the last 12 months. This is strong evidence of long-term stagnation for a dependency.
Only one registry account has publishing access. That is a thin publishing base for a user-owned project and leaves limited visible redundancy if the maintainer becomes unavailable.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old release, this indicates little ongoing maintenance.
The linked repository name does not match the package name and its README does not mention the package. That makes package ownership and source correspondence less clear.
The repository uses Composer, which fits the package ecosystem, but it reports no security scanning tools. That weakens maintenance hygiene without independently making the package unfit.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
elefant/app-installer Version * | — | — |
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.