Package Health/pushinbr/pam-native-scanner

pushinbr/pam-native-scanner

This release appears usable and reasonably well maintained, with five releases over 36 days, recent repository activity, a non-archived repository, strong package and repository scaffolding, explicit Apache-2.0 licensing, minimal runtime dependencies, and secure-looking workflow permissions. The main concerns are its very young age, pre-1.0 version, all 13 recent commits coming from one contributor, no repository security policy, and no security-scanning tooling; the organization backing provides some maintenance context but does not eliminate the bus-factor risk. Overall, it is a promising but still immature dependency whose API and maintenance continuity should be monitored.

Latest v0.3.2

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Five releases in 36 days with a median interval of about 7 days indicates active early development, although the short history does not yet demonstrate long-term continuity.

Repo bus factor

One contributor accounts for 100% of the recent commits. Organization backing partially compensates for this concentration, but no second active contributor is shown.

Repo commit activity

Thirteen commits in the last three months, all from one active maintainer, demonstrate recent maintenance but also leave continuity dependent on a single contributor.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured, leaving a security-hygiene gap.

Security policy

The repository has no security policy, which weakens vulnerability-reporting and response transparency; this is a hygiene concern rather than evidence of unsafe code.