The project is only 50 days old, with four releases clustered in two days and six commits in three months. Strong documentation, tests, licensing, and read-only workflow permissions help, but action references are unpinned.
70%
Total Score
67
100
83
83
The package and repository are owned by the same individual account, with no organization backing shown. This does not invalidate the project, but it provides no organizational redundancy for the concentrated maintainer base.
The package is only 50 days old and has four releases, with a median interval of about 1.5 hours. This shows active initial development but provides little long-term maintenance history.
One contributor made all six commits in the last three months. With no second active contributor or organizational backing shown, maintenance depends heavily on one person.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance gap, not a severe risk by itself.
The single workflow was fully analyzed, uses read-only permissions, and has no high- or medium-confidence audit findings. However, both analyzed action references are unpinned, leaving a mild reproducibility and workflow-supply-chain gap.
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.