tigress/router

This is a usable but lightly evidenced package: it has a clear GPL-3.0-or-later license, stable non-prerelease versions, a recent release, no deprecation, minimal runtime dependencies, and a linked non-archived repository whose README identifies the package. However, the repository has had no commits or active maintainers in the last 3 months, has no tests, changelog, security policy, or security scanning, and shows essentially no adoption. The small, single-user project may still be suitable for a low-risk dependency, but its limited maintenance and transparency evidence make it a cautious choice for critical applications.

Latest 2026.09.03.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A README is present and documents installation and usage, but neither the artifact nor repository contains tests or a changelog; for a routing component, the lack of tests is a meaningful maintenance gap.

Project backing

The repository is owned by a user account rather than an organization, providing limited evidence of institutional backing or maintainer redundancy.

Repo commit activity

There were 0 commits and 0 active maintainers in the last 3 months, which is the strongest maintenance concern despite the recent registry release.

Repo popularity

The repository has 0 stars and 0 forks, with 1 watcher; popularity is only supporting evidence, but these values provide little external validation or community resilience.

Repo tooling

Composer is used as a build tool, but no security scanning tool is configured; the build setup is appropriate while security assurance is limited.