The MIT license, clear README, changelog, and security tooling improve transparency. The organization backing offsets the recent single-contributor activity, while unpinned workflow actions remain a modest maintenance concern.
78%
Total Score
67
100
100
75
All recent commits came from one contributor, creating concentration risk. Organization ownership provides some ability to hand off maintenance, so this is a caution rather than a severe risk.
There was one commit in the last 3 months, so recent source activity is present but thin. The regular release history partly offsets this limitation.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, but it is not evidence of abandonment by itself.
The single workflow was fully analyzed with no untrusted checkout, injection, or high-confidence audit findings. However, all four referenced actions are unpinned, leaving a modest supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
sulu/sulu Version ^2.6 | — | — |
sulu/automation-bundle Version ^2.1 | — | — |
symfony/framework-bundle Version ^6.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.