stayforlong/finite-guzzlehttp

Release historydanger

The package has had only one release, published nearly seven years ago, with no releases in the last 12 months. That is strong evidence of abandonment for a dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the nearly seven-year-old release and indicating inactive maintenance.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than decisive, but these figures provide no evidence of a broader support base.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a meaningful transparency gap for an old dependency, though it is not severe on its own.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This adds a modest maintenance concern.