Complete tests, documentation, licensing, and a security policy improve transparency. The small release history and five months without commits leave maintenance capacity uncertain; workflow actions are also unpinned.
70%
Total Score
67
100
89
100
The package and repository are owned by the same individual account, so the source relationship is clear, but there is no organizational backing shown to broaden maintenance capacity.
The package has existed for about nine years but has only four releases, with a median interval of about 18 months. One release in the last 12 months shows activity, but the cadence is sparse.
There were no commits and no active maintainers in the last three months. Combined with the sparse release history, this weakens evidence of current maintenance capacity.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence of abandonment.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, injection findings, or audit errors. However, all three action references are unpinned, leaving the workflow exposed to mutable action changes.
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.