t3n/seo-routing

Documentation and tests support straightforward adoption, with a small dependency footprint and a matching source repository. The project has been inactive for about three years, so future compatibility and fixes are uncertain.

Latest 4.0.1

Packagist

65%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was about three years ago, with no releases in the last 12 months. Earlier releases were regular enough to show prior maintenance, but the prolonged pause raises abandonment risk.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the long release pause. This materially lowers confidence in ongoing maintenance.

Repo issue activity

There was no issue or pull-request activity in the last month, while one issue and two pull requests remain open. This adds modest evidence of stalled maintenance.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. That is a hygiene gap rather than a severe dependency risk, especially given the package's small file tree.

Security policy

The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap, not evidence that the package is unsafe.