The package includes tests, release notes, a clear Apache-2.0 license, and no install-time scripts. Its last release was nearly 10 years ago, repository commits stopped about 7 years ago, and the repository does not identify the package in its README.
42%
Total Score
0
75
75
The latest release was in October 2016, with no releases in the last 12 months. This long release gap materially raises abandonment risk.
There were no commits or active maintainers in the last 3 months, consistent with repository inactivity for about 7 years. This is a substantial abandonment concern.
The repository name does not match the package name and its README does not mention the package. That weakens provenance confidence, even though a subpackage can legitimately use a different repository name.
Composer is used for the build, but no security scanning tools are reported. The missing scanning is a modest hygiene gap, not a standalone adoption blocker.
The repository has no security policy. This is a transparency gap, though it is less significant than the prolonged release and commit inactivity.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
rhubarbphp/rhubarb Version ^1.1.0 | — | — |
rhubarbphp/module-leaf Version ^1.0.0@dev | — | — |
rhubarbphp/module-stem Version ^1.0.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.