The project has clear documentation, release notes, tests in the repository, and regular recent releases. Maintenance is concentrated in one active contributor, while workflows use 19 unpinned actions and install packages outside lockfiles.
70%
Total Score
75
94
75
The package defines post-install and post-update Composer scripts. These add installation-time behavior that consumers must account for, although the signal alone does not show that the scripts are unsafe.
Only one registry account has publishing access. The repository is organization-owned, which provides some backing, but publishing continuity still depends on a narrow registry maintainer base.
All 46 recent commits came from one contributor. Organization ownership partly mitigates handoff risk, but no second active contributor is shown, so continuity remains a concern.
Composer build tooling is present, but no security-scanning tool was detected. The missing scanner is a hygiene gap rather than evidence of abandonment.
All six workflows were analyzed, but all 19 action references are unpinned, one workflow has top-level write permissions, and high-confidence template-injection findings plus ad hoc package installs were reported. No pull_request_target, workflow_run, untrusted checkout, or script-injection path was found, so this is workflow hygiene and supply-chain exposure rather than a severe standalone risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ray/di Version ^2.23.0 | — | — |
ray/aop Version ^2.19 | — | — |
bear/sunday Version ^1.8 | — | — |
bear/package Version ^1.20 | — | — |
bear/app-meta Version ^1.9 | — | — |
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.