portrino/impersonate

Repo commit activitycaution

There were 0 commits and 0 active maintainers in the last 3 months, which is a meaningful maintenance-continuity concern. The recent repository push and current release provide partial counterevidence but do not erase the period of observed inactivity.

Repo popularitycaution

The repository has only 3 stars and 8 forks, so external adoption signals are limited. Popularity is supporting evidence only, and the package's long release history and recent releases reduce the significance of this weakness.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning capability is a repository hygiene gap for a package handling user impersonation.

Security policycaution

The repository has no security policy. This reduces transparency around vulnerability reporting and response expectations, particularly for an extension with authentication-related functionality.

Token permissionscaution

Neither analyzed workflow declares top-level token permissions. Although no workflow requests top-level write access and no dangerous workflow patterns were found, explicit least-privilege permissions would provide stronger CI/CD hygiene.