Usable with caveats: it is actively released, clearly documented, licensed, and not deprecated or archived. The main concerns are that it is only 54 days old, all recent commits come from one contributor, and the repository has no security policy or scanning tools.
74%
Total Score
50
100
88
83
The registry namespace and repository owner match, but both are user-owned rather than organization-backed. This supports package identity while offering limited evidence of backup maintenance capacity.
The package is young at 54 days with four releases, including a release today, showing active early development. Its short history leaves limited evidence of long-term maintenance.
All recent commits came from one contributor, so maintenance depends heavily on a single person. The matching registry and repository user provides ownership continuity but does not reduce the single-contributor risk.
There was one commit in the last three months, but it was made recently and the repository also shows four merged pull requests in the last month. This supports current activity but not yet a deep maintenance track record.
The repository uses Composer build tooling, but no security scanning tools are present. For this small package that is a transparency gap rather than a severe supply-chain risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
neos/neos Version ^9.1 | — | — |
medienreaktor/neos-studio Version ^1.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.