The package is clearly licensed and documented, with no install-time scripts or deprecation notice. Its small, inactive repository and absent security scanning leave maintenance capacity uncertain.
61%
Total Score
0
81
75
The repository recorded no commits and no active maintainers in the past three months; combined with the last push being about four months ago, this is meaningful evidence of stalled maintenance.
Ten releases arrived during the package's first 20 days, showing an active initial development burst, but the package is still young at about five months old and offers limited long-term evidence.
Composer build tooling is present, but no security-scanning tool was detected. That is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, not a standalone adoption blocker.
Version 0.3.1 is not a stable major release, so the public API may still change; it is not marked as a prerelease, which partly offsets that concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
flightphp/core Version ^3.0 | — | — |
flightphp/runway Version ^1.1 | — | — |
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.