The package is clearly tied to its matching repository and has a stable 1.0.0 release with a license and changelog. Its workflow has no detected dangerous findings, but all four action references are unpinned. The organization-backed project should be checked for continued maintenance before adoption.
62%
Total Score
67
100
78
75
The artifact includes a README and changelog, while the missing package tests are normal packaging practice. Repository tests are also absent, so this provides documentation but limited testing evidence.
This is the package's only release, published 488 days ago, with no releases in the last 12 months. That leaves meaningful uncertainty about ongoing maintenance despite the stable version.
No commits and no active maintainers were recorded during the last three months. Combined with the single old registry release, this is the strongest maintenance concern.
No new or closed issues or pull requests were recorded in the last month, and there were no merged pull requests. This gives little evidence of active community maintenance, although the open-issues count is unknown.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, so this limits external validation but does not by itself make the package unhealthy.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.75.0 | — | — |
spryker/company Version ^1.5.0 | — | — |
spryker/propel-orm Version ^1.17.0 | — | — |
spryker/file-manager Version ^2.3.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.