rainlab/user-plugin

This is a healthy, actively maintained release with a long release history, frequent recent releases, stable versioning, an unarchived matching repository, and current commit and issue activity from two active contributors. The organization-backed project and repository/package alignment reduce concerns from the small registry maintainer list and concentrated commit share. The main reservations are the absence of a security policy, undeclared top-level GitHub Actions permissions, and no configured security-scanning tool, but these are hygiene gaps rather than evidence of abandonment or an unfit dependency.

Latest v3.7.1Packagist

Health Score Breakdown

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool is configured. This is a modest supply-chain hygiene gap, not evidence that the package is unmaintained.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a genuine transparency and maintenance-process gap.

Token permissionscaution

The only workflow lacks top-level permissions, although no workflow requests top-level write access and no dangerous workflow patterns were found. The configuration is less explicit than preferred but presents limited observed risk.

View all 20 health checks

Maintainers

Alexey Bobkov

Samuel Georges

Direct Dependencies

Dependency	Last Release	Score
october/rain Version >=3.0	—	—
firebase/php-jwt Version ^6.4 || ^7.0	—	—
pragmarx/google2fa Version ^8.0 || ^9.0	—	—
bacon/bacon-qr-code Version ^2.0 || ^3.0	—	—
composer/installers Version ~1.0	—	—

View All 6 Dependencies