The missing security policy and security scanning reduce transparency for a package that runs background jobs, while its tests, documentation, organization backing, and recent release provide meaningful support. The dependency set is small and installation has no lifecycle scripts.
67%
Total Score
67
100
88
83
The package has existed for about 7 years with 6 releases and one release in the last 12 months; the latest release is recent, but the overall cadence is modest.
There were 0 commits and 0 active maintainers in the last 3 months, which weakens evidence of ongoing maintenance despite the recent release and repository push.
The repository has 25 open issues and 1 open pull request, with no issues or pull requests opened or merged in the last month; this suggests limited current engagement.
Composer build tooling is present, but no security scanning tools were detected, leaving a security-process gap for a package that runs scheduled jobs.
The repository has no security policy, so users have no documented private reporting path or stated security-response process.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version ^1.0 || ^2.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.