The project has clear documentation, tests in the repository, a license, and a recent release. Maintenance capacity is less reassuring because no commits or active maintainers were recorded in the last three months, while the workflow uses four unpinned actions and has no security policy or scanning.
68%
Total Score
75
100
89
75
No commits or active maintainers were recorded in the last three months. This weakens evidence of ongoing maintenance, although the package also published a release during the assessment period.
The repository has zero stars, one fork, and one watcher. This is weak supporting evidence, but popularity alone does not determine the health of a small package.
Composer build tooling is present, but no security scanning tools were detected, leaving security-maintenance coverage less transparent.
The repository has no security policy. This is a transparency and vulnerability-reporting gap, though it is not evidence that the package is unsafe.
The single workflow was fully analyzed with no injection or high-severity findings, but all four action references are unpinned. The lack of a top-level permissions block is acceptable on its own and no write-wide token was observed.
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.