peehaa/async-twitter
The README reports only 40% API coverage and explicitly says not to use the package yet. Tests and release notes provide some structure, but the repository does not name or mention this package, adding uncertainty about its fit.
30%
Total Score
0
60
50
Health Score Breakdown
The package has had no releases in the last 12 months, and its latest release was in May 2017 despite being more than 10 years old. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and showing no recent maintenance capacity.
The artifact and repository include a README and tests, and this version has GitHub release notes. However, the README reports only 40% API implementation and explicitly advises against use, materially limiting the positive evidence.
The repository name does not match the package name and its README does not mention the package. Although this can occur with subpackages, no provided evidence confirms that relationship here.
The linked repository has no security policy. This is a transparency and maintenance gap, though it is secondary to the much stronger abandonment evidence.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Pieter Hordijk |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 amphp/amp Version ^1 | — | — |
amphp/artax Version ^2 | — | — |
daverandom/exceptional-json Version ^1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 9 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.