tempest/router

This release appears healthy and reasonably safe to depend on: it is actively maintained, with 59 commits from 7 maintainers in the last 3 months, 99 releases over 561 days, and 81 releases in the last 12 months. The package is stable, not deprecated, licensed under MIT with a license file, backed by an organization-owned repository, and has no install-time lifecycle scripts. The main concerns are concentration of activity in one contributor, absence of a security policy and security-scanning tooling, and limited artifact documentation; however, repository tests and strong recent maintenance partially compensate for those hygiene gaps.

Latest v3.19.2

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact lacks a README, tests, and changelog, which reduces release transparency, but repository tests are present and compensate for the most important testing gap.

Repo bus factor

One contributor made about 81% of the 59 recent commits, creating concentration risk. The other six active contributors and organization ownership provide partial mitigation, but the concentration still warrants caution.

Repo popularity

The repository has only 1 star and 0 forks, so external popularity is limited, but popularity is supporting evidence and does not outweigh the strong activity indicators.

Repo tooling

Composer is used as a build tool, but no security-scanning tools are reported; this is a transparency and security-hygiene gap rather than evidence of abandonment.

Security policy

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.