The project has a clear README, changelog, MIT license, and recent repository activity. Organization backing helps, but only one release and one active contributor leave limited evidence of long-term maintenance. The repository’s failure to identify the package clearly and its unpinned workflow actions add transparency and build-hygiene concerns.
66%
Total Score
67
81
50
This is a 70-day-old package with only one release, so there is little release history to demonstrate sustained maintenance or compatibility work.
All three recent commits came from one contributor. Organization ownership provides some handoff capacity, but no second active contributor is shown.
The repository had three commits in the last three months, showing some recent activity, but that is limited evidence for a package with only one release.
The repository name does not match the package name and its README does not mention the published package, so the package-to-source relationship is not clearly established.
Composer build tooling is present, but no security-scanning tool was detected, leaving a modest transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
shopware/core Version ~6.6.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.