Integration of prunner (an embedded pipeline task runner) in Neos
68%
Total Score
caution
Usable with caveats: recent releases continue, but repository activity is sparse and concentrated in one contributor.
The release has four runtime dependencies, including core framework, HTTP, and JWT libraries; this is a meaningful dependency surface but not unusually large for the package's integration role.
All one recent commit came from a single contributor, creating concentration risk; the organization-owned repository provides some capacity to hand maintenance off.
Only one commit was recorded in the last three months, which indicates limited recent development despite the recent release history.
Composer build tooling is present, but no security-scanning tools were detected, leaving a modest transparency and maintenance gap.
The repository has no security policy, so users have no documented reporting or response process; the absence of this policy is a real but not severe health concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
neos/flow Version * | — | — |
neos/neos Version ^7.0 || ^8.0 | — | — |
firebase/php-jwt Version ^7.0 | — | — |
guzzlehttp/guzzle Version ^7.3 | — | — |
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.