Tests, a clear license, and a small dependency surface make the package straightforward to inspect. The organization-owned repository and matching package references add useful provenance, but no security policy leaves a modest transparency gap.
47%
Total Score
75
100
79
75
The latest release was about three years and six months ago, with no releases in the last 12 months. Although 23 releases show an established history, the prolonged release gap raises abandonment risk.
The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap. This is a meaningful maintenance concern for a package used as a Composer plugin.
The repository has zero stars and forks and one watcher. Low popularity is only supporting evidence, but it offers little external evidence of active adoption to offset the stale maintenance record.
Composer is used as a build tool, but no security scanning tools were detected. The missing scanning is a modest hygiene gap, not evidence that the package is unsafe to depend on.
The repository has no security policy. For a small plugin this is a limited transparency gap, but it leaves no documented process for reporting or handling vulnerabilities.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.