nml/whatsapp-notifier

This is a usable but very new package with good basic transparency: it has an MIT declaration, a substantial README, tests in both the artifact and repository, a coherent file tree, and no install-time lifecycle scripts or dangerous workflows. However, v1.0.2 is the only release and the package is 0 days old, so there is no demonstrated maintenance history; repository activity and popularity are also currently zero, and the project has only one registry maintainer. The absence of security scanning and a security policy adds a smaller hygiene concern. Adoption is reasonable for evaluation or controlled use, but the package should be monitored closely before becoming a critical dependency.

Latest v1.0.2

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publish access. This is not evidence of unsafe administration by itself, but it indicates a thin publishing base and limited continuity if the maintainer becomes inactive.

Project backing

The repository is owned by an individual user rather than an organization, so institutional backing is not demonstrated; this reinforces the continuity concern alongside the single maintainer and zero activity.

Release history

The package is 0 days old with only one release, so it has no demonstrated release track record or maintenance history; this is a meaningful maturity concern.

Repo commit activity

There were 0 commits and 0 active maintainers in the last 3 months. The package's 0-day age explains this result, but it still leaves maintenance capacity unproven.

Repo issue activity

There are no issues or pull requests and no activity in the last month; given the repository's 0-day age this is inconclusive rather than severe, but it does not demonstrate an active support community.