unlcms/unl_user

Usable with caveats: the package is licensed, tested, clearly backed by its matching organization repository, and has released three times in the last year. Recent repository activity is quiet and there is no security policy or automated security scanning, so ongoing maintenance should be verified before adopting it.

Latest 1.11

Packagist

70%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded no commits and no active maintainers during the last 3 months. The regular release history partly compensates, but this still leaves a meaningful recent-maintenance concern.

Repo issue activity

There was no issue or pull request activity in the last month, with one issue still open. This is a modest maintenance signal, though the package's release history shows that the project is not abandoned.

Repo tooling

Composer is used for builds, but no security scanning tool is configured. For a module handling LDAP user data, the absence of automated security checks is a meaningful hygiene gap.

Security policy

The repository has no security policy. This reduces transparency about how vulnerabilities should be reported, although it does not by itself indicate that the package is unsafe.