It has tests, a clear README, an MIT license, and no install-time scripts. Organization backing and a recent release reduce abandonment concerns, but security scanning and a security policy are absent.
68%
Total Score
75
86
75
All 5 commits in the last 3 months came from one contributor, leaving maintenance dependent on a single active individual. Organization ownership provides some continuity, but no second active contributor is shown.
Composer build tooling is present, but no security scanning tools were detected. This is a maintenance and transparency gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a modest transparency concern for a library dependency.
Version 0.2.0 is not a stable major release, so API compatibility may still change. It is not marked as a prerelease, which partly offsets that concern.
The only workflow was fully analyzed and has no injection or high-severity findings, but both of its 2 action references are unpinned, weakening build reproducibility and trust.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
fakerphp/faker Version ^v1.19.0 | — | — |
symfony/property-info Version ^v5.4 || ^v6.0 || ^v7.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.