pushinbr/pam-desktop

This release appears generally suitable to depend on: it is an actively published, stable-major package with 22 releases over 44 days, recent repository activity, clear licensing, substantial documentation and tests, and no deprecation or archival status. The main concerns are that the project is very young, all 71 recent commits came from one maintainer despite organization ownership, the repository has no security-scanning tooling or security policy, and two workflows request top-level write permissions. These issues warrant review for a production dependency, but the observed maintenance and transparency signals outweigh them.

Latest v1.3.4

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is only 44 days old, which limits maturity evidence, but 22 releases in that period demonstrate active publication rather than abandonment.

Repo bus factor

All 71 recent commits came from one contributor, creating a meaningful continuity and review risk; organization ownership partly mitigates handoff risk but does not provide evidence of a second active maintainer.

Repo popularity

The repository has only 1 star and no forks or watchers, indicating limited external adoption; this is supporting caution rather than a decisive health failure for a young package.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected, leaving a security-hygiene gap for a package with native and capability-boundary code.

Security policy

No repository security policy was found, reducing vulnerability-reporting transparency and incident-response visibility.