Clear licensing, tests, documentation, and release notes support adoption, while the small release history limits maturity evidence. The workflow is audited cleanly for dangerous behavior, but its eight action references are all unpinned and the repository has no security policy or scanning.
62%
Total Score
50
83
50
The package has only two releases over about 13 months, with one release in the last 12 months and a median interval of about 162 days. That is limited evidence of maturity and sustained maintenance.
The repository had zero commits and zero active maintainers in the last three months. Combined with the sparse release history, this weakens confidence in ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected. For a development fixture library this is a modest repository-hygiene gap, not evidence of abandonment by itself.
No security policy was found in the repository. This reduces transparency around vulnerability reporting, although it is less material for a test-fixture package than for a production-facing service.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all 8 action references are unpinned, which leaves avoidable build-integrity risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
fakerphp/faker Version ^1.9.1 | — | — |
magento/framework Version ^103.0.4 | — | — |
magento/module-quote Version ^101.2.4 | — | — |
magento/module-sales Version ^103.0.4 | — | — |
magento/module-catalog Version ^104.0.4 | — | — |
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.