The MIT license, focused README, and organization-owned repository make the package transparent to inspect. Its small dependency set and lack of install scripts reduce integration risk, but the project shows no current maintenance capacity.
38%
Total Score
50
100
81
75
The latest release was published in March 2018, with no releases in the last 12 months. This roughly eight-year gap is strong evidence of abandonment for a package developers may need to maintain alongside current Neos versions.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but it shows no observed ongoing development.
Composer is used as the build tool, which fits the package ecosystem. No security scanning tools were detected, a minor transparency and hygiene gap that matters less than the clear maintenance slowdown.
The linked repository has no security policy. This is a transparency gap, though the package's lack of recent activity is the more significant adoption concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
neos/flow Version * | — | — |
neos/neos Version 3.* | — | — |
neos/nodetypes Version * | — | — |
flowpack/listable 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.