goletter/hyperf-exception-notify
The MIT license, matching repository, and detailed README make the package straightforward to evaluate and integrate. Its short release history, one recent commit from one contributor, and lack of a security policy leave maintenance capacity lightly evidenced.
62%
Total Score
50
88
50
Health Score Breakdown
The package is about 338 days old but has only two releases, with roughly 317 days between them; this provides limited evidence of an established release cadence.
One contributor made all commits in the last three months, leaving maintenance dependent on a single individual with no demonstrated handoff capacity.
Only one commit was recorded in the last three months, so current maintenance activity is present but very limited.
Composer build tooling is present, but no security scanning tools were detected; this is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy, so users have no documented vulnerability-reporting process or disclosure expectations.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 hyperf/di Version ^3.1 | — | — |
hyperf/cache Version ^3.1 | — | — |
hyperf/redis Version ^3.1 | — | — |
hyperf/config Version ^3.1 | — | — |
hyperf/logger Version ^3.1 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 11 months ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.