bleicker/response
The repository has no security scanning and no security policy, leaving little visible oversight for future changes. Its zero runtime dependencies reduce integration risk, but the project shows no recent maintenance capacity.
32%
Total Score
0
100
60
50
Health Score Breakdown
The package has made no release in more than 11 years: its latest release was May 13, 2015, with zero releases in the last 12 months. 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 gap since the latest release and indicating no current maintenance capacity.
No declared license, license file, or repository license file was detected. That leaves the legal terms for using this dependency unclear.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide no sign of an active user or contributor community.
The repository has no security policy, so there is no documented channel or process for reporting and handling vulnerabilities. This is a transparency gap, though it is less serious than the lack of maintenance.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Carsten Bleicker |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 11 years ago
- Created
- 11 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.