Which has better activity and maintenance signals?

Based on the RepoPilot analysis and repository data:

practical-tutorials/project-based-learning shows stronger maintenance signals:

1. Active automation: The repository runs a dedicated link-rot workflow that performs automated sweeps to detect and fix broken links. This includes state tracking and auto-fix capabilities for confirmed-dead entries and redirects.

2. PR lifecycle management: An active stale-prs workflow manages pull requests with a 90-day stale threshold and 30-day close window, with explicit exemptions for PRs labeled keep-open. This shows deliberate maintenance overhead.

3. Link validation scripting: The repository contains a substantial check_readme.py script with functions like _retry_after_seconds() [L605-L616], normalize_no_scheme() [L187-L191], and domain_in_policy() [L218-L229]—evidence of ongoing infrastructure for quality assurance.

sindresorhus/awesome has different signals:

1. Linting integration: A repo_linter.sh workflow validates new entries against awesome-lint before merge.

2. Strict PR requirements: Detailed pull_request_template.md with extensive checks (30-day existence, no AI-generation, proper formatting, license requirements).

However, practical-tutorials/project-based-learning's continuous link-rot detection and automated remediation appears more active and maintenance-intensive than awesome's entry-validation approach, suggesting higher ongoing operational commitment.

FOLLOW_UPS:

• What's the current link-rot status in project-based-learning?
• How many active maintainers does practical-tutorials have?
• Which repo has higher issue/PR response times?