The MIT license, README, tests, and matching repository support adoption. But the project has had no recent commits or releases, and all three workflow actions are unpinned, so future fixes and build integrity are uncertain.
46%
Total Score
25
83
50
The latest release was over three years ago, with no releases in the last 12 months and only two releases overall. This is strong evidence of an inactive release process.
The repository had zero commits and zero active maintainers in the last three months, reinforcing the long release gap and increasing abandonment risk.
Only one user account has registry publish access. That is a thin publishing base for an independently owned project and offers limited continuity if the maintainer stops work.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a transparency gap, though it is less significant than the inactivity evidence.
The single workflow was fully analyzed with no dangerous findings, but all three action references are unpinned. This leaves the build exposed to changing action code despite otherwise clean workflow hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
cycle/orm Version ^2.2 | — | — |
symfony/cache Version ^5.4 || ^6.0 | — | — |
symfony/config Version ^5.4 || ^6.0 | — | — |
cycle/annotated Version ^3.2 | — | — |
symfony/console Version ^5.4 || ^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.