Documentation, tests, a changelog, and clear MIT licensing are in place. Recent maintenance is sparse and concentrated in one contributor, while the workflow has an unpinned dependency and a script-injection concern.
65%
Total Score
75
50
88
50
Five runtime dependencies form a moderate dependency surface for a Laravel generator package; this is manageable but adds maintenance exposure compared with a self-contained package.
The package has 46 releases over about two and a half years, but only 2 releases in the last 12 months, indicating a materially slower recent cadence despite its established history.
All recent commits came from one contributor, creating a low individual redundancy signal; organization ownership partly offsets the risk because maintenance can potentially be handed off.
Only 1 commit was recorded in the last 3 months, which is thin recent development activity for a package with an ongoing release history.
Composer build tooling is present, but no security-scanning tools were detected, leaving a security-process gap for a package that generates application code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/dbal Version ^3.6 || ^4.0 | — | — |
symfony/process Version ^6.0 || ^7.0 || ^8.0 | — | — |
illuminate/support Version ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0 | — | — |
javaabu/generator-helpers Version ^1.3 | — | — |
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.