Documentation and tests are present, and the repository is not archived. Unpinned workflow actions, no security policy, and a single active contributor add maintenance and release-process risk.
58%
Total Score
83
75
83
The assessed release is v3.0.0-BETA1, and the package README explicitly warns that this development branch should not be used in production. That makes the release materially less suitable than a stable version.
The package has 27 releases and a historical median interval of about 48 days, but no registry release in the last four years. Recent repository commits partly compensate for the stale release cadence, but do not replace a maintained release.
All 10 recent commits came from one contributor, leaving maintenance highly concentrated. Organization backing provides some handoff capacity, but no second active contributor is shown.
The repository name does not match the package name and its README does not mention the package, creating some uncertainty that the linked repository is the actual source for this release.
The workflow audit completed cleanly with no untrusted checkouts, script injections, or high-confidence findings, but all three referenced actions are unpinned. That leaves avoidable build reproducibility and supply-chain hygiene risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
twig/twig Version ^2.12.0|^3.0 | — | — |
doctrine/orm Version ^2.9 | — | — |
symfony/form Version ^5.4|^6.0 | — | — |
symfony/intl Version ^5.4|^6.0 | — | — |
doctrine/dbal Version ^2.13.1|^3.2 | — | — |
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.