pengzekuan/wechat
The MIT declaration, matching repository, and repository tests provide basic transparency, and installation has no lifecycle scripts. A single maintainer, no security policy or scanning, and negligible repository activity leave little evidence of ongoing stewardship.
30%
Total Score
25
75
50
Health Score Breakdown
The latest release was published about 10 years ago, with only two releases overall and none in the last 12 months. This is strong evidence that the package is no longer actively maintained.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and indicating no recent maintenance capacity.
Only one registry maintainer is listed, leaving a thin publishing base and increasing continuity risk for an already inactive package.
Composer build tooling is present, but no security scanning tool was detected. That leaves a modest supply-chain hygiene gap without proving the package is unsafe.
The repository has no security policy, reducing transparency for reporting and handling vulnerabilities. This is a secondary concern because the dominant risk is the lack of recent maintenance.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 peter |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 10 years ago
- Created
- 10 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.