abuseio/findcontact-ripe
The package has a clear README, a coherent file tree, and a small runtime dependency set. Its source and release history show no activity since August 2016, leaving compatibility and maintenance uncertain.
38%
Total Score
50
100
72
75
Health Score Breakdown
The latest release was published in August 2016, and there have been no releases in nearly 10 years. This is strong evidence of abandonment for a package that may need to track PHP or API changes.
The repository had zero commits and zero active maintainers in the last three months. Combined with the last push in 2016, this indicates a severe maintenance and abandonment risk.
The repository has zero stars and forks and only two watchers. Popularity is supporting evidence rather than a verdict, but these counters provide no meaningful community signal to compensate for inactivity.
Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are present. The missing scanning is a hygiene weakness rather than proof of unsafe code.
The linked repository is not archived, which is a positive sign, but its last push was in August 2016 and therefore does not offset the evidence of inactivity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 AbuseIO Foundation |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 jover/ripe-stat Version 0.1.* | — | — |
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.