em4nl/uresponse
The project has one maintainer, one star, and no security policy, limiting confidence in long-term support. A clear README, MIT license, and comprehensive tests provide useful adoption evidence despite the age.
42%
Total Score
38
100
67
83
Health Score Breakdown
The latest of only three releases was published in March 2019, with no releases in over seven years. This is strong evidence of abandonment for a dependency consumers may need maintained over time.
There were no commits and no active maintainers in the last three months, consistent with the release history showing no releases for over seven years.
Only one registry account has publish access. This is a thin publishing base and increases continuity risk when combined with the absence of recent activity.
The repository is owned by an individual user rather than an organization, so there is no demonstrated organizational backing to compensate for the single-maintainer model.
There are no open issues or pull requests and no recent activity. The clean tracker is not evidence of active maintenance in this otherwise inactive project.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Emanuel Tannert |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 7 years ago
- Created
- 7 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.