graciousstudios/api

Release historydanger

The package has six releases but none in the last 12 months, and its latest release was about 8 years ago. This is strong evidence of abandonment risk despite the package not being deprecated.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long release gap and leaving compatibility issues unlikely to receive attention.

Repo issue activitycaution

There are nine open pull requests with no new or merged pull requests in the last month. This suggests unresolved maintenance demand, although there are no open issues.

Repo popularitycaution

The repository has 1 star, 0 forks, and 7 watchers, indicating limited observable adoption. Popularity is supporting evidence rather than decisive on its own, but it does not offset the maintenance concerns.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. That is a modest transparency and hygiene gap rather than a standalone reason to reject the package.