mnib-dev/urgentcargus
The package is small, clearly documented, and has a focused dependency set. Its release history is sparse, and recent work comes from one contributor; the missing security policy and scanning add modest maintenance risk.
66%
Total Score
50
100
75
75
Health Score Breakdown
The package has only 3 releases over about 4 years, with a median interval of about 851 days, although 2 releases arrived in the last 12 months. This suggests an infrequent but recently renewed release pattern.
All recent commits came from one contributor, giving the project a bus factor of one. The repository owner is an individual, so there is no provided organization backing to offset this concentration.
The repository recorded 1 commit in the last 3 months from 1 active maintainer. Recent activity is present, but the volume is too limited to demonstrate strong ongoing maintenance capacity.
Composer is used as a build tool, but no security-scanning tools are configured. This is a modest transparency and maintenance gap rather than evidence that the release is unsafe.
The repository has no SECURITY.md or other security policy. That weakens vulnerability-reporting transparency, though it is not by itself evidence of abandonment.
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 ^6.0 || ^7.0 || ^8.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 days 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.