galek/coding-standard

Release historydanger

The latest release was over five years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a package intended as a maintained coding standard.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long release gap rather than showing ongoing maintenance.

Repo issue activitycaution

There were no new or merged pull requests in the last month. This supports the maintenance concern, although issue data is partly unknown because the open issue count was unavailable.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, providing little external evidence of adoption or community support. Popularity is supporting evidence, so this is a secondary concern.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The build setup is positive while the missing scanning reduces transparency around ongoing dependency and code checks.