Organization backing, a README, release notes, and a clean Composer package make it understandable to adopt. A missing security policy leaves less guidance for reporting vulnerabilities.
61%
Total Score
75
100
81
75
The package has five releases, but its latest release was about 20 months ago and there were no releases in the last 12 months, indicating reduced maintenance activity.
There were no commits and no active maintainers in the measured three-month period, which is a concrete sign that maintenance has slowed substantially.
Composer is used for the build, but no security scanning tooling is present. The missing scanning is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The repository has no security policy, leaving contributors and users without a documented vulnerability-reporting process.
Version 0.3.0 is not a stable-major release, which suggests a less mature compatibility commitment, although it is not marked as a prerelease.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
neos/flow Version 7.* || 8.* || @dev | — | — |
flownative/prometheus Version 0.* || @dev | — | — |
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.