Its MIT license and compact configuration-focused file set make the release easy to inspect. However, the project has had no releases or repository commits since May 2019 and lacks a security policy, creating substantial maintenance risk.
38%
Total Score
50
100
60
83
Only three releases were published, all during May 2019, with no release in more than seven years. That strongly raises abandonment risk, despite the package reaching a stable 1.0.2 version.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. Organization backing is present, but no observed activity shows current maintenance capacity.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, secondary to the much stronger inactivity evidence.
The repository is not archived, which avoids a direct unfitness signal, but its last push was in May 2019 and reinforces the inactivity concern from the release and commit history.
No repository security policy was found. For a package with no recent maintenance activity, this leaves vulnerability reporting and response expectations unclear.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
neos/flow Version ~4.0 || ~5.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.