sponsor-finder
Find which of a GitHub repository's dependencies are sponsorable via GitHub Sponsors. Uses deps.dev API for dependency resolution across npm, PyPI, Cargo, Go, RubyGems, Maven, and NuGet. Checks npm funding metadata, FUNDING.yml files, and web search. Verifies every link. Shows direct and transitive dependencies with OSSF Scorecard health data. Invoke with /sponsor followed by a GitHub owner/repo (e.g. "/sponsor expressjs/express").
Profile →npx skills add github/awesome-copilot --skill sponsor-finder --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Sponsor Finder Discover opportunities to support the open source maintainers behind your project's dependencies. Accepts a GitHub `owner/repo` (e.g. `/sponsor expressjs/express`), uses the deps.dev API for dependency resolution and project health data, and produces a friendly sponsorship report covering both direct and transitive dependencies. ## Your Workflow When the user types `/sponsor {owner/repo}` or provides a repository in `owner/repo` format: 1. **Parse the input** — Extract `owner` and `repo`. 2. **Detect the ecosystem** — Fetch manifest to determine package name + version. 3. **Get full dependency tree** — deps.dev `GetDependencies` (one call). 4. **Resolve repos** — deps.dev `GetVersion` for each dep → `relatedProjects` gives GitHub repo. 5. **Get project health** — deps.dev `GetProject` for unique repos → OSSF Scorecard. 6. **Find funding links** — npm `funding` field, FUNDING.yml, web search fallback. 7. **Verify every link** — fetch each URL to confirm it's live. 8. **Group and report** — by funding destination, sorted by impact. --- ## Step 1: Detect Ecosystem and Package Use `get_file_contents` to fetch the manifest from the target repo. Determine the ecosystem a
- Your Workflow
- Step 1: Detect Ecosystem and Package
- Step 2: Get Full Dependency Tree (deps.dev)
- URL encoding
- For repos without a single root package
- Step 3: Resolve Each Dependency to a GitHub Repo (deps.dev)
- Efficiency rules
- Step 4: Get Project Health Data (deps.dev)
- Step 5: Find Funding Links
- 5a: npm funding field (npm ecosystem only)
- 5b: .github/FUNDING.yml (repo-level, then org-level fallback)
- 5c: Web search fallback
- Step 6: Verify Every Link (CRITICAL)
- Step 7: Output the Report
What does the sponsor-finder skill do?
Find which of a GitHub repository's dependencies are sponsorable via GitHub Sponsors. Uses deps.dev API for dependency resolution across npm, PyPI, Cargo, Go, RubyGems, Maven, and NuGet. Checks npm funding metadata, FUNDING.yml files, and web search. Verifies every link. Shows direct and transitive dependencies with OSSF Scorecard health data. Invoke with /sponsor followed by a GitHub owner/repo (e.g. "/sponsor expressjs/express").
How do I install it?
Run `npx skills add github/awesome-copilot --skill sponsor-finder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.