kusabi/http

Release historydanger

There has been only one release, published about seven years ago, with no releases in the last 12 months. This is strong evidence of an immature or abandoned dependency.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months. Combined with the old release history, this indicates stalled maintenance.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap for a network-facing HTTP library.

Version stabilitycaution

Version 0.0.1 is not a stable major release, which adds compatibility risk for a library with only one published version.

Workflow auditcaution

Both workflows were analyzed successfully and have no dangerous triggers or audit findings. However, all seven action references are unpinned, creating avoidable build-reproducibility and supply-chain hygiene risk.