lipemat/wp-phpcs

Project backingcaution

The repository is owned by a user rather than an organization, so the concentrated maintainer activity is not mitigated by visible organizational backing.

Repo bus factorcaution

One contributor made all 14 commits in the last 3 months, creating a genuine single-maintainer continuity risk for a user-owned project.

Repo toolingcaution

Composer build tooling is present, supporting reproducible project management, but no security scanning tools were detected, leaving a modest security-process gap.

Security policycaution

The repository has no security policy, reducing vulnerability-reporting transparency and maintainer guidance for security issues.

Token permissionscaution

The sole workflow lacks top-level token permissions declarations. Although no top-level write permissions were observed, explicit least-privilege configuration would provide stronger CI security hygiene.