The repository has no recorded commits in the last three months, although the package was first released today and has a second release, so maintenance is not yet proven. Licensing, documentation, tests, changelog, organization backing, and package alignment are all solid; the missing security policy is a smaller transparency gap.
68%
Total Score
75
100
88
83
The package is 0 days old with two releases published today, including this version, so there is too little history to establish long-term maintenance.
There were zero commits and zero active maintainers in the last three months. The same-day release history explains why this is not evidence of abandonment, but it leaves maintenance capacity unproven.
Composer build tooling is present, but no security scanning tool was detected, leaving a modest project-hygiene gap.
The repository has no security policy, so it does not document a clear process for reporting or handling vulnerabilities.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
verbb/base Version ^3.0 | — | — |
craftcms/cms Version ^5.3.0 | — | — |
craftcms/commerce Version ^5.0.0 | — | — |
guzzlehttp/guzzle Version ^7.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.