The package is clearly documented, licensed, and backed by an organization, with recent repository activity. However, its release history is stale, maintenance is concentrated in one contributor, and the workflow uses an unpinned container image.
62%
Total Score
83
100
86
67
The package has only three releases, with no release in more than three years and a median interval of about 427 days. This is a meaningful maintenance concern, though recent repository activity partly offsets the stale registry history.
All three recent commits came from one contributor, leaving maintenance highly concentrated. Organization backing provides some handoff capacity but does not remove the continuity concern.
Composer build tooling is present, but no security-scanning tool is reported. This is a modest transparency gap rather than evidence of abandonment.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
All workflows were analyzed, but all seven action references are unpinned and the audit found a high-confidence unpinned container image. One workflow also grants top-level write access, although job-level or read-only permissions are used elsewhere.
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.