Usable with caveats: the package is clearly identified, licensed, tested in its repository, and has no deprecation or workflow red flags. It has only one release, no releases in the last 12 months, no recent commits, and a single publisher, so long-term maintenance is uncertain.
62%
Total Score
50
100
75
75
Only one registry account has publishing access. The matching repository is user-owned rather than organization-backed, so there is limited visible publishing redundancy.
The registry namespace and repository owner match, and the repository is user-owned. This supports package identity but does not provide organizational maintenance capacity.
This is the only release, published about 14 months ago, with no releases in the last 12 months. That leaves limited evidence of ongoing maintenance.
There were no commits and no active maintainers in the last 3 months. Combined with the single-release history, this raises abandonment risk.
The repository uses Composer build tooling, but no security scanning tools were detected. The missing scanning is a transparency gap, though it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
hosmelq/sse Version ^0.1.0 | — | — |
saloonphp/saloon Version ^3.14 | — | — |
thecodingmachine/safe Version ^3.3 | — | — |
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.