The repository has no commits or active maintainers in the last three months, despite three releases in the past year. Licensing, tests, documentation, and a non-deprecated repository are reassuring, but missing security scanning and unpinned workflow actions reduce transparency.
68%
Total Score
67
100
94
83
The repository is owned by an individual account rather than an organization, so the small registry maintainer list is not clearly backed by a larger project team. The package nevertheless has a named team and recent release history.
There were zero commits and zero active maintainers in the last three months. This is a meaningful maintenance concern, although the recent release indicates the project has not completely stopped publishing.
Composer build tooling is present, but no security scanning tools were detected. That leaves an avoidable gap in repository hygiene.
The repository has no security policy. This weakens vulnerability-reporting transparency for a package that processes generated documents and depends on a bundled Java component.
The sole workflow was fully analyzed with no dangerous triggers or audit findings, but all 3 of 3 action references are unpinned. The missing top-level permissions block is acceptable on its own, while unpinned actions remain a supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/framework-bundle Version ^6.0.4||^7.0||^8.0 | — | — |
matthiasnoback/symfony-config-test Version ^6.1.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.