A stable release, clear licensing, useful release notes, and an active repository improve transparency. Open-source security practices are limited, and recent work is concentrated in one contributor.
68%
Total Score
63
100
93
83
All four recent commits came from one contributor, giving the project a single-person maintenance dependency. Organization backing provides some handoff capacity, but no second recent contributor is shown.
Four commits were made in the past 3 months, so maintenance is not absent. The activity is relatively light for a maintained integration package.
The repository has eight open issues but no new or closed issues and no merged pull requests in the past month. This suggests limited visible issue-management activity despite the recent release.
Composer build tooling is present, but no security-scanning tools were detected. This is a transparency and maintenance gap rather than evidence of unsafe code.
The repository has no security policy, leaving vulnerability-reporting expectations unclear for consumers and maintainers.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
neos/neos Version ^8.3 | — | — |
neos/neos-ui Version ^8.3 | — | — |
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.