Documentation, licensing, repository ownership, and release notes are solid. The project is brand new, with only two releases and no established commit history; its workflow also leaves one action unpinned.
65%
Total Score
83
100
88
75
The package is 0 days old with only 2 releases, so there is not yet enough release history to demonstrate sustained maintenance. The recent second release and detailed notes provide some evidence of active initial development.
The repository shows 0 commits and 0 active maintainers over the last 3 months. Because the package is newly released, this is more a lack of an established maintenance record than evidence of a long-term collapse.
Composer build tooling is present, but no security scanning tools were detected. The build setup is a positive, while the missing scanning is a modest transparency gap for a payment-related plugin.
The repository has no security policy. That leaves vulnerability-reporting expectations undocumented, although it does not by itself show that the package is unsafe.
The workflow audit completed fully with no dangerous triggers, untrusted checkouts, script injection, or audit findings, and it scopes permissions at job level. Its one action is unpinned, leaving a modest reproducibility and workflow supply-chain gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
craftcms/cms Version ^5.0.0 | — | — |
craftcms/commerce Version ^5.0.0 | — | — |
bacon/bacon-qr-code Version ^3.0 | — | — |
tecnickcom/tc-lib-barcode Version ^2.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.