atoms/testing

This is a young but currently healthy and actively maintained package. It has eight releases over 22 days, 22 repository commits in the last three months, two active maintainers, an organization-owned repository, a matching README, tests, a clear MIT license, no install-time lifecycle scripts, and no registry deprecation or archive status. The main reservations are its short operating history, zero recorded popularity, lack of security scanning and a security policy, and no recent issue or pull-request activity; these reduce maturity and transparency somewhat but do not currently indicate abandonment or that the package is unfit to depend on.

Latest 0.6.0

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Eight releases in 22 days with a median interval of about 1.5 days show active development, but the 22-day package age leaves limited evidence of long-term stability.

Repo issue activity

There were no new or closed issues or pull requests in the last month, and no pull requests were merged; this provides little evidence of an active user-support channel.

Repo popularity

The repository has zero stars, forks, and watchers. This is weak supporting evidence, though low popularity alone does not establish poor health for a young, specialized package.

Repo tooling

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

Security policy

The repository has no security policy, reducing transparency about vulnerability reporting and response procedures.