The MIT license, release notes, and recent Neos 9 update improve transparency. Organization ownership and a small dependency surface provide some continuity, despite limited repository safeguards.
72%
Total Score
83
100
81
50
The package has existed since January 2021 and released once in the last 12 months, but its median release interval is about 329 days, indicating a slow maintenance cadence.
All four recent commits came from one contributor, leaving maintenance dependent on a single active person and increasing continuity risk.
The repository name does not match the package name and its README does not mention the package, making the package-to-source relationship less transparent even though the repository path is otherwise specific.
Composer build tooling is present, but no security scanning tools are reported, leaving a modest gap in repository safeguards.
No security policy is present in the repository, reducing transparency for reporting and handling vulnerabilities.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
neos/neos-ui Version ~9.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.