Vet a package before you depend on it — report in Slack
Type a package name — via Firecrawl the scenario finds its page and GitHub, gathers fresh numbers and sends a verdict to Slack: is it actively maintained and worth building on.
The check takes a minute, not an hour
Live numbers from the GitHub, not gut feeling
A plain-language verdict, not a spreadsheet
If the package doesn't exist, you're told right away