The MIT license, matching repository, README, and organization backing provide basic transparency. The project is too new to establish maintenance, while the repository has no security policy or scanning tools, leaving modest gaps.
55%
Total Score
75
88
75
The package is only 1 day old, with 4 releases in that time and a median interval of about 2 hours. This shows active initial publishing but provides too little history to establish dependable maintenance.
No commits or active maintainers were observed during the last 3 months. Because the repository is only 1 day old, this is mainly a lack of maintenance evidence rather than proof of abandonment.
Composer build tooling is present, but no security scanning tools were detected. That leaves a modest project-hygiene gap for a package intended to be reused.
The repository has no security policy. This weakens vulnerability-reporting transparency, although it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
wexample/symfony-user Version >=7.0.0 | — | — |
wexample/symfony-loader Version >=14.0.0 | — | — |
wexample/symfony-helpers Version >=11.0.0 | — | — |
wexample/symfony-routing Version >=1.0.0 | — | — |
wexample/symfony-design-system Version >=21.0.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.