Its small scope and clear README make the intended use easy to understand. There is little evidence of ongoing engineering support, so future framework changes may be yours to handle.
38%
Total Score
0
50
50
The package has only two releases, both published about 20 minutes apart, and no release in roughly 3 years and 5 months. That strongly suggests abandonment, although the repository is not archived.
The repository recorded zero commits and zero active maintainers in the last 3 months, with its last push in April 2023. This confirms the long release gap is not just a registry-publishing issue.
The repository has zero stars and forks and only one watcher, so there is little visible community support to compensate for inactive maintenance. Popularity is supporting evidence rather than a verdict on its own.
Composer build tooling is present, but no security-scanning tool was detected. That weakens maintenance and release assurance, with no provided compensating security evidence.
The linked repository has no security policy, leaving no documented route for reporting vulnerabilities. This is a transparency gap, though it is less serious for a small demonstration projection.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
neos/flow Version * | — | — |
neos/contentrepository-core Version * | — | — |
neos/contentrepositoryregistry Version * | — | — |
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.