Maintenance is quiet despite a long project history and a recent release, while the repository remains active enough to avoid abandonment concerns. Tests, clear licensing, and organization backing help, but the workflow uses an unpinned container image and lacks a security policy.
67%
Total Score
75
100
88
67
The package has existed for about 10 years with 21 releases, but only 1 release in the last 12 months. The recent release is reassuring, though the slower cadence warrants caution for a maintained integration.
The repository recorded zero commits and zero active maintainers in the last 3 months. Although the December 2025 release shows some recent project activity, the current maintenance signal is weak.
Composer build tooling is present, but no security scanning tools were detected. For a small adapter this is a transparency and maintenance gap rather than evidence of unsafe code.
The repository has no security policy. This makes vulnerability reporting and response expectations less clear, especially for a package used in production integrations.
The only workflow was fully analyzed with no untrusted triggers or script-injection sinks, but its container image is unpinned with high confidence. That weakens build reproducibility and workflow supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
fusio/engine Version ^6.0 | — | — |
pda/pheanstalk Version ^8.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.