The repository remains active, documented, tested, and clearly tied to the package. Security scanning is absent, all five workflow actions are unpinned, and recent work comes from one contributor, so future maintenance and build assurance depend heavily on the same person.
72%
Total Score
75
100
88
75
The package and repository are owned by the same individual account, so there is no organizational backing shown to offset the concentrated maintainer base.
The package has eight releases since April 2021, but none in the last 12 months; the latest registry release is over 18 months old, which raises maintenance concerns despite recent repository activity.
All three recent commits came from one contributor, so maintenance capacity is concentrated and a maintainer outage could delay fixes.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest gap in project assurance.
The repository has no security policy, reducing clarity about how vulnerabilities should be reported and handled.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.