Risky to adopt: the package has had no release or repository activity for about 11 years, with only one registry maintainer. Good documentation, tests, licensing, and a matching repository reduce transparency concerns but do not offset the abandonment risk.
42%
Total Score
25
69
The latest release was published about 11 years ago, and there have been no releases in the last 12 months. This is strong evidence that the package is no longer actively maintained.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long release gap. The repository is not archived, but there is no recent development activity to compensate.
Only one registry account has publishing access. That is a thin publishing base and increases continuity risk, although the matching source repository provides some ownership transparency.
Composer is used for builds, which is appropriate, but no security scanning tools are present. This is a modest transparency and maintenance gap rather than a severe risk by itself.
The linked repository is not marked archived, but its last push was about 11 years ago. The non-archived status avoids an additional severe risk but does not indicate current maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
phalcon/incubator Version 1.3.4 | — | — |
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.