ml/fgc-client

Release historydanger

The package has only two releases, with the latest nearly ten years ago and no releases in the last 12 months. This is strong evidence of abandonment risk despite the stable 1.0.1 version.

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the last three months, consistent with the latest release being nearly ten years ago. This materially increases abandonment and compatibility risk.

Repo popularitycaution

The repository has one star, zero forks, and one watcher, providing little evidence of a broad user or contributor base to sustain the project.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are present. The missing scanning is a hygiene gap, while the long inactivity remains the more important concern.

Security policycaution

The repository has no security policy. For an HTTP client, this weakens the documented path for reporting and handling vulnerabilities.