wangrunxinyes/whyperf-base
The package has a clear license, a matching repository, and a working Composer build, but its README is only 15 characters and no security scanning is configured. Its single-user maintainer base also leaves little resilience if maintenance stops.
34%
Total Score
33
100
63
67
Health Score Breakdown
The package has had only two releases, both in May 2021, with no release in over five years. That long gap is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's multi-year release pause.
The package runs post-autoload-dump and post-root-package-install scripts, increasing installation-time behavior that consumers must trust. No provided signal shows these scripts are harmful, so this is a hygiene concern rather than a severe risk.
Only one registry maintainer is listed, so the project has limited redundancy if that person becomes unavailable. The matching personal repository provides some ownership context but does not offset the thin base.
A README is present, but it contains only the package heading and provides no usage guidance. The absence of tests and a changelog in the published artifact is normal packaging practice and is not penalized.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 wangrunxin |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 wangrunxinyes/whyperf-core Version 1.0.9 | — | — |
Weekly Downloads
Info
- Last Published
- 5 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.