txiki/router

Release historydanger

The package has had only two releases, with the latest published in February 2015 and none in the last 12 months. This is strong evidence of abandonment risk for a dependency, despite the stable 1.0.1 version.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since February 2015.

Maintainerscaution

One registry maintainer is a thin publishing base, although the linked repository is owned by the same individual, so this is a modest capacity concern rather than evidence of a broken project.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. That weakens ongoing maintenance assurance, particularly for a project with no recent activity.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap, but not a severe risk by itself.