spaze/phpcs-phar

Project backingcaution

The repository is owned by a user account, not an organization, so there is no observed organizational backing to compensate for the single-contributor maintenance model.

Repo bus factorcaution

One contributor made all commits in the last three months, so maintenance depends entirely on a single person; the repository owner is an individual rather than an organization that could more readily hand work off.

Repo commit activitycaution

Only one commit was made in the last three months, showing limited recent development activity; this is partly consistent with a release-focused artifact but still weak evidence of maintenance capacity.

Repo toolingcaution

The project uses Composer for builds but reports no security scanning tools, leaving a meaningful transparency and detection gap for an automated release artifact.

Security policycaution

The repository has no security policy, reducing clarity about how vulnerabilities should be reported and handled.