The project has a recent stable release, tests, release notes, and a matching repository. Its small current contributor base and unpinned workflow actions leave avoidable maintenance and build-integrity concerns.
74%
Total Score
88
100
94
67
Only one contributor made all six recent commits, creating a narrow maintenance base. Organization backing partly compensates because maintenance can potentially be handed off, but the current concentration remains a caution.
Composer build tooling is present, but no security scanning tools were detected. For a small package this is a transparency and monitoring gap rather than a severe dependency risk.
The repository has no published security policy. That weakens vulnerability-reporting transparency, although it does not by itself indicate abandonment or unsafe code.
Both workflows were analyzed successfully with no untrusted checkouts, script injection, or audit findings, and neither grants top-level write permissions. However, all four referenced actions are unpinned, leaving workflow builds exposed to action changes over time.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
leafs/anchor Version ^5.0 | — | — |
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.