The README, changelog, matching repository, and organization ownership provide useful transparency. Its stable 1.0.0 release has no recent release or commit activity, while security documentation and scanning are absent.
60%
Total Score
50
100
88
83
There were zero commits and zero active maintainers in the last three months. Together with no releases in the last 12 months, this materially raises abandonment risk.
The package has 12 releases since October 2021, but none in the last 12 months; the latest release was August 27, 2025. This indicates a meaningful maintenance slowdown.
There are two open issues, with no new or closed issues and no pull requests in the last month. This suggests limited current project interaction, though the small issue count is not severe by itself.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance weakness rather than proof of unsafe code.
The repository has no security policy. That reduces disclosure transparency for a package used in development workflows, but it is not independently severe.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
neos/flow Version * | — | — |
neos/neos 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.