No release has appeared since 2018, and recent repository activity is absent, leaving maintenance uncertain. The README names other packages and the repository does not mention this package; organization backing and MIT licensing help, but do not resolve the abandonment and ownership concerns.
38%
Total Score
75
57
75
The package has only two releases, both in November 2018, and none in the last 12 months. This long release gap materially raises abandonment risk.
A README is present and the package has a GitHub release for this version. However, the README refers to other package names and gives an unrelated Composer install command, weakening consumer transparency.
There were zero commits and zero active maintainers in the last three months, consistent with a project that has not received recent maintenance.
The repository name does not match the package name and its README does not mention the package, so the repository may not clearly belong to this release.
Composer is used as a build tool, but no security-scanning tools are configured. The missing scanning is a hygiene gap rather than evidence of abandonment by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.0.0 | — | — |
spryker/glossary Version ^3.0.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.