goenitz/request

Release historydanger

The package has only two releases, with the latest published in May 2017 and none in the last 12 months. This is strong evidence of abandonment risk for a dependency taken today.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with a project that has been inactive for years. This materially increases abandonment risk.

Repo popularitycaution

The repository has one star, zero forks, and one watcher, providing little evidence of a broad user or contributor base. Low popularity is supporting evidence rather than a verdict by itself.

Repo toolingcaution

The repository uses Composer but has no security-scanning tooling. For a dependency that handles request and uploaded-file data, the lack of automated security oversight is a meaningful hygiene gap.

Security policycaution

The repository has no security policy. This weakens vulnerability-reporting transparency, although it is less serious than the clear maintenance inactivity.