openclerk/users

The package has a clear README and a GPL-3.0 license. Organization backing and a matching repository improve traceability, but the lack of security tooling leaves older code harder to assess.

Latest 0.1.1

Packagist

40%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases exist, with none in the last 12 months and a median interval of about 868 days; the latest release was about nine years ago. This is strong evidence of abandonment risk.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and providing no evidence of current maintenance.

Repo popularity

The repository has zero stars, two forks, and one watcher. Popularity is supporting evidence rather than a verdict, but these very low figures provide little evidence of a broad active user base.

Repo tooling

Composer build tooling is present, which supports reproducible project structure, but no security scanning tools are configured. The build support partly compensates for the tooling gap.

Repository archived

The linked repository is not archived, which avoids a formal abandonment marker. Its last push was about nine years ago, so the unarchived status is only limited compensation.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

Dependency	Last Release	Score
openclerk/db Version ^0.1	—	—
openclerk/config Version ^0.1	—	—
openclerk/events Version ^0.2	—	—
league/oauth2-client Version ~0.6	—	—
soundasleep/lightopenid Version dev-master	—	—