The single-person project has limited recent activity and no security scanning, while its workflow leaves all four action references unpinned. Clear licensing, tests, documentation, and a non-archived repository provide useful support.
58%
Total Score
50
83
One registry maintainer account is responsible for publishing the package, which creates a thin publishing base. The linked repository is owned by the same individual, so this is a modest resilience concern rather than evidence of a broken project.
The package has made no release in more than three years, with only three releases overall and none in the last 12 months. This is a meaningful maintenance concern, though the repository remains active enough to have been pushed in December 2024.
There were no commits and no active maintainers in the last three months, indicating currently stalled development. The repository is not archived, but that does not offset the lack of recent work.
Composer build tooling is present, but no security scanning tools were detected. That leaves a transparency and maintenance gap for a package intended to be used as a dependency.
The only workflow was fully analyzed and has no untrusted checkout, injection, or high-severity findings, but all four action references are unpinned. The absence of a top-level permissions block is acceptable here because no broad write access was detected.
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.