The project is clearly documented and backed by an organization, with repository tests and a security policy. Maintenance is limited to security fixes, with no releases or commits in the last 12 months; workflow dependencies are also unpinned.
62%
Total Score
67
100
88
100
The package has had no releases in the last 12 months, despite a 32-day median release interval across its history. This supports the stated security-only maintenance posture and lowers confidence in ongoing feature work.
The repository recorded zero commits and zero active maintainers in the last three months. This is consistent with security-only maintenance but still indicates little capacity for regular fixes or improvements.
There were no newly opened or closed issues or pull requests in the last month, while six pull requests remain open. This suggests limited current project throughput.
Composer build tooling is present, but no security-scanning tools were detected. The security policy partly compensates through documented reporting guidance, but automated coverage is not evident.
All three workflows were analyzed without audit findings or untrusted-code sinks, but all three action references are unpinned and one workflow grants top-level write permissions. These are workflow hygiene concerns rather than a severe risk because no dangerous trigger or sink was detected.
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.