The artifact includes tests and has a focused runtime dependency, while the repository remains unarchived and organization-backed. Its license is absent and maintenance has effectively stopped, leaving legal and abandonment concerns.
40%
Total Score
0
100
50
50
Neither the package nor the linked repository contains a declared or detected license file. This creates a concrete legal and transparency concern for adoption.
The latest release was in July 2019, with no releases in the last 12 months despite 32 historical releases. This long gap is strong evidence of abandonment risk.
There were zero commits and zero active maintainers in the last three months. Combined with the old latest release, this materially increases the risk that issues will not be addressed.
The repository name does not match the package name and its README does not mention the package. The organization backing and coherent package contents reduce the concern, but ownership remains less transparent.
The repository uses Composer for builds, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than proof of unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
unite-cms/core-bundle Version 0@dev | — | — |
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.