wpify/php-scoper

Repo bus factorcaution

All recent commits came from one contributor, creating a real continuity risk. Organization backing provides some ability to hand off maintenance, which partly compensates for the concentration.

Repo popularitycaution

The repository has no stars or forks and only one watcher. This is weak supporting evidence, though low popularity is not decisive for a narrowly scoped organization-maintained wrapper.

Repo toolingcaution

The repository uses Composer build tooling, but no security scanning tools were detected. The absence of scanning is a transparency and assurance gap, though the package's small automated wrapper scope limits its weight.

Security policycaution

No security policy was found in the repository. This reduces transparency about vulnerability reporting and response, although the package is a small wrapper rather than a broad application framework.

Token permissionscaution

The only workflow lacks top-level token permissions, so its permissions are not explicitly constrained at the workflow level. No top-level write access was observed, but the missing declaration is still a minor hardening gap.