spartan/router

Release historydanger

The package has only 3 releases, with no release in nearly four years and a median release interval of about 898 days. This is strong evidence of abandonment risk for a dependency that may need fixes.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, confirming that development is currently inactive rather than merely releasing infrequently.

Maintainerscaution

Only one registry account has publish access. This is a thin publishing base and increases continuity risk, although the linked repository is clearly identified with the same project.

Repo popularitycaution

The repository has 0 stars, 0 forks, and 1 watcher, providing no meaningful community adoption or outside maintenance signal. Popularity is supporting evidence, but this reinforces the broader maintenance concern.

Security policycaution

The repository has no published security policy, leaving no documented reporting or response process. This is a transparency gap, especially for a routing library exposed to application traffic.