wangrunxinyes/hyperf-tcc
The README and MIT declaration make setup and licensing clear. The one-person project has little adoption and no security policy, leaving limited evidence of ongoing support for a transaction component.
38%
Total Score
0
79
50
Health Score Breakdown
The package is about 4 years and 10 months old, with all 7 releases ending on November 24, 2021 and none in the last 12 months. This is strong evidence that maintenance has stopped.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the release history showing no activity since November 2021.
The repository has 1 star, 0 forks, and 0 watchers, so there is little visible community adoption or support to offset the stale maintenance record.
The repository has no security policy or security-scanning tools. That is a meaningful transparency gap for a component handling distributed transactions, although it is not evidence of malicious behavior.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 h6play |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 hyperf/nsq Version ~2.1 | 2.2.* | — | — |
hyperf/redis Version ~2.1 | 2.2.* | — | — |
hyperf/logger Version ~2.1 | 2.2.* | — | — |
hyperf/database Version ~2.1 | 2.2.* | — | — |
hyperf/snowflake Version ~2.1 | 2.2.* | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 5 years 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.