asgard/http

Release historydanger

The latest release was published in May 2016, with no releases in the last 12 months and only four releases overall. This is strong evidence of abandonment risk, despite the package not being registry-deprecated.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long period without releases. This materially reduces confidence in ongoing maintenance.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counters provide no additional confidence alongside the inactivity signals.

Repo toolingcaution

The repository uses Composer build tooling, which supports reproducible package management, but it has no security scanning tools. This is a secondary hygiene gap rather than a standalone adoption blocker.

Security policycaution

No security policy is present in the repository, leaving vulnerability-reporting guidance unclear. This is a transparency weakness, though the license and repository tests provide some compensating project structure.