compwright/should-retry
Usable with caveats: the package is licensed, documented, tested, and backed by a matching repository, but it has had only one release and no commits for about 18 months. Very low project adoption and limited security-policy and workflow-permission hygiene add maintenance risk.
64%
Total Score
75
75
75
Health Score Breakdown
This is the only release, published about 18 months ago, with no releases in the last 12 months. That limited history makes long-term maintenance uncertain.
There were no commits and no active maintainers in the last three months. For a package with only one release, this is a meaningful indication of uncertain ongoing maintenance.
The repository has 1 star, 0 forks, and 1 watcher. Popularity is not decisive, but these very low figures provide little supporting evidence of community review or shared maintenance.
The repository uses Make and Composer build tooling, but no security-scanning tools were detected. This is a transparency and assurance gap rather than evidence that the package is unsafe.
The linked repository is not archived, although its last push was about 18 months ago, consistent with the package's limited recent activity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Jonathon Hill |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 psr/log Version ^1.0 || ^2.0 || ^3.0 | — | — |
psr/http-client Version ^1.0 | — | — |
psr/http-message Version ^1.0 || ^2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 1 year 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.