pushinbr/pam-native-auth

This release appears usable and reasonably well-supported: it is not deprecated or archived, has a matching repository, clear licensing, comprehensive documentation, tests, changelog, native source files, and active recent release and pull-request activity. The main risks are that the package is only 36 days old, remains below a stable major version, all recent commits come from one contributor, and the repository has no security policy or security-scanning tooling. Organization ownership and read-only workflow permissions provide some mitigation, but the package still warrants monitoring before becoming a critical dependency.

Latest v0.3.2

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Six releases in 36 days, with a median interval of about 2 days, show active development, although the short history provides limited evidence of long-term maintenance.

Repo bus factor

One contributor made all 15 recent commits, creating a concentrated maintenance dependency. Organization ownership offers some handoff potential, but no second active contributor is shown.

Repo commit activity

There were 15 commits in the last three months, demonstrating recent work, but all activity came from one active maintainer.

Repo popularity

The repository has zero stars, forks, and watchers. This is weak supporting evidence of adoption, but popularity is not decisive and the package is very new with active commits and releases.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured, leaving a security-hygiene gap for a package handling authentication and credential storage.