anver/getresponse

Release historydanger

The package has had only two releases, both in March 2019, and none in roughly seven years. This is strong evidence of abandonment risk for a library dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No provided maintenance signal compensates for this inactivity.

Licensecaution

The manifest declares MIT, but the artifact license file was detected as GPL-3.0, creating a material licensing conflict that should be resolved before use. A license file exists, so this is ambiguity rather than an absence of licensing.

Repo popularitycaution

The linked repository has one star and no forks, offering little supporting evidence of broad community use or independent review. Popularity is only supporting evidence, so this does not determine the verdict alone.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap, although the small project size limits how much weight it carries.