gourmet/common

Release historydanger

The latest release was published in June 2014, with no releases in the last 12 months. This long period without releases is strong evidence of abandonment risk.

Repository archiveddanger

The repository is not archived, but it was last pushed in September 2014. The visible repository state therefore does not offset the prolonged lack of maintenance.

Repo issue activitycaution

There are no open issues or pull requests and no issue or pull-request activity in the last month. Combined with the old last push, this reinforces the maintenance concern.

Repo popularitycaution

The repository has only 1 star, 1 fork, and 1 watcher. Popularity is supporting evidence rather than a verdict, but these figures provide little evidence of a broad active user base.

Repo toolingcaution

Composer is used for builds, but no security scanning tools are present. For an old package this is a modest transparency and maintenance gap, not evidence of maliciousness.