The repository has no security policy or security scanning, and its modest popularity offers little outside validation. Licensing, tests, release notes, and organization backing provide useful transparency.
42%
Total Score
50
100
81
75
The latest release was about 11 years ago, with no releases in the past 12 months. This is strong evidence that compatibility and maintenance may have been abandoned.
There were no commits or active maintainers in the past 3 months, consistent with a repository whose last push was about 8 years ago. This materially raises abandonment risk.
There has been no issue or pull-request activity in the past month, with two issues still open. This adds some evidence of limited maintenance, though it is less decisive than the stale release and commit history.
Composer build tooling is present, but no security scanning tools were detected. For a small PHP bridge this is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy. That reduces transparency around vulnerability reporting and response, especially for a package with no recent maintenance evidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
zfr/rbac Version ^1.2 | — | — |
prooph/service-bus Version >=4.3 <6.0 | — | — |
zf-commons/zfc-rbac Version ^2.5.2 | — | — |
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.