cubes-doo/my-dhl
The repository has almost no community activity and no security policy. A clear MIT license, working README, and organization-owned source provide useful transparency, but maintenance evidence is too old for a dependable choice.
40%
Total Score
75
75
50
Health Score Breakdown
The latest release was in December 2020, with no releases in the last 12 months despite nine historical releases. This long release gap is strong evidence of abandonment risk.
There were no new or closed issues or pull requests in the last month, and only one issue is open. This indicates little visible community or maintainer activity.
Four stars, three forks, and one watcher show a very small user and contributor footprint. Low popularity is not disqualifying alone, but it provides little evidence of ongoing support.
Composer build tooling is present, but no security-scanning tools were detected. That limits evidence of routine security maintenance, though it is not severe by itself.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a package that connects to a shipping API.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 5 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.