Its release history is sparse and recent repository activity is absent. The organization-owned repository matches the package and includes a usable README, but testing and security-process evidence is limited.
58%
Total Score
83
100
81
75
A 1,311-character README explains command usage and configuration. The package and repository report no tests or changelog, leaving limited validation and release-history documentation for a database-affecting command.
The package has only 3 releases over 527 days, with 1 release in the last 12 months and a median interval of about 203 days; this indicates a small, slow-moving project rather than an established release cadence.
There were 0 commits and 0 active maintainers in the last 3 months. With only one release in the last year, this is meaningful evidence of slow or paused maintenance.
Composer is used for builds, but no security-scanning tooling is present. That is a process gap, though it is not evidence that the release is unsafe by itself.
The repository has no security policy, reducing transparency about vulnerability reporting and maintenance response.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
fakerphp/faker Version ^1.24 | — | — |
typo3/cms-core Version ^14.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.