Recent releases, a clear MIT license, and a documented 2026 release support ongoing maintenance. The single active contributor, absent security policy, and workflow hygiene issues leave meaningful operational risk.
65%
Total Score
50
50
100
83
Thirteen runtime dependencies, including Symfony, Doctrine, and several related jawira packages, create a relatively broad dependency surface for a bundle. The profile is plausible for its functionality but increases maintenance coupling.
Only one registry account, Jawira Portugal, has publish access. Because the repository owner is an individual rather than an organization, this represents a limited publishing base.
The registry namespace and repository are both owned by the same individual account, so there is no shown organizational backing to compensate for the concentrated maintainer base.
All three recent commits came from one contributor, giving the project a 100% top-contributor share and leaving little demonstrated redundancy for maintenance.
There were three commits in the last three months, showing some recent maintenance, but the volume is low for a project with active releases.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/orm Version ^2.9 || ^3.0 | — | — |
jawira/db-draw Version ^2.0 | — | — |
symfony/config Version ^7.0 || ^8.0 | — | — |
symfony/console Version ^7.0 || ^8.0 | — | — |
jawira/entity-draw Version ^2.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.