happyyyyyyyyy/ethereum-client
The repository has no security policy or automated security scanning, and its 10-file tree is minimal. The MIT license, README, and lack of install scripts reduce adoption friction, but the project shows little evidence of ongoing care.
42%
Total Score
69
75
Health Score Breakdown
The package has only one release, published nearly five years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a package handling Ethereum transactions.
The repository has zero stars and zero forks, with one watcher. Popularity is only supporting evidence, but these counts provide little evidence of community review or adoption.
Composer build tooling is present, but no security scanning tools are configured. That is a maintenance and transparency gap for a package handling cryptographic and transaction-related code.
The repository is not archived, which is a positive, but it was last pushed nearly five years ago. Its inactive state reinforces the lack of ongoing maintenance.
No security policy was found. For a package that handles private keys and transaction signing, this leaves vulnerability reporting and maintenance expectations unclear.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.0.1 | — | — |
kornrunner/keccak Version ^1.0 | — | — |
simplito/elliptic-php Version ^1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 4 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.