Documentation and licensing are in place, with tests in the repository and a clear v2.0.0 release note. The small dependency set and organization backing reduce adoption friction, but CI should be tightened before relying on automated publishing.
58%
Total Score
75
100
88
83
All 9 analyzed action references are unpinned, and one workflow combines a pull_request_target trigger with top-level write permissions. The high-confidence bot-conditions finding is a further workflow hygiene concern, though no untrusted checkout or script injection was detected.
The package has existed for about 4 years and has two releases in the last 12 months, but its median release interval is about 197 days, indicating a relatively slow cadence.
The repository had no commits and no active maintainers in the last 3 months. This is a meaningful maintenance concern, although the latest release was published about six months ago.
Composer build tooling is present, but no security scanning tools were detected, leaving a repository-security hygiene gap.
The repository has no SECURITY policy, reducing transparency about vulnerability reporting and response expectations.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
azuyalabs/yasumi Version ^2.10 | — | — |
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.