gourmet/faker

Release historydanger

The package has had no release in more than 11 years, with all four releases concentrated in April 2015. That strongly increases abandonment and compatibility risk.

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 and unlikely to receive fixes.

Repo issue activitycaution

There are two open issues and no issues or pull requests were changed in the last month, adding evidence of inactivity rather than active support.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are reported. This is a modest transparency and maintenance gap, not a standalone adoption blocker.

Repository archivedcaution

The linked repository is not archived, but its last push was in August 2016, so the non-archived status does not demonstrate active maintenance.