devbeta/psr12-strict-rules

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the old last-push date, this is strong evidence that maintenance has effectively stopped.

Project backingcaution

The package and repository are owned by the same individual account, which supports identity alignment but does not provide organizational backing or a broad succession path.

Release historycaution

The package has had only four releases, with none in the last 12 months; its latest recorded release was about four years and ten months ago. This indicates substantial staleness for a package that may need updates as tooling evolves.

Repo popularitycaution

The repository has one star and one fork, providing little evidence of broad community support or a backup maintainer base. Low popularity is supporting evidence only, but it leaves the project with few visible adoption signals.

Repo toolingcaution

The repository uses Composer for builds, which fits the package ecosystem, but no security-scanning tools were detected. The missing scanner is a hygiene gap rather than evidence of an unsafe release.