MIT licensing, tests, a changelog, and recent releases support straightforward adoption. The single registry maintainer and absent security policy leave less independent oversight.
68%
Total Score
75
100
89
83
There were no commits and no active maintainers in the last three months. This weakens confidence in ongoing maintenance, despite the recent registry release.
The repository has 1 star and no forks, providing little community validation or external maintenance support. Popularity is supporting evidence only, so this is a modest concern.
Composer build tooling is present, but no security scanning tools were detected. That is a hygiene gap rather than evidence of an unsafe release.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This lowers transparency but is not severe on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
oasis/event Version ^3.0 | — | — |
oasis/logging Version ^3.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.