sponsor-finder

You can find sponsorship opportunities by analyzing a GitHub repository's direct and transitive dependencies. The tool retrieves funding metadata from sources like the deps.dev API, FUNDING.yml files, and npm metadata to identify which dependencies are sponsorable.

Dependency sponsorship verification works by querying the deps.dev API and checking multiple funding metadata sources like FUNDING.yml and npm metadata. It validates all discovered funding links before reporting to ensure sponsorship opportunities are active and legitimate.

Yes, you can check project health data for dependencies using OSSF Scorecard integration. The analysis retrieves maintenance status and security metrics alongside sponsorship data to help you assess the health of dependency projects before contributing.

The best way to identify sponsorable dependencies across ecosystems is using a tool that scans both direct and transitive dependencies via the deps.dev API. It cross-references multiple funding sources like GitHub Sponsors and FUNDING.yml to map the complete sponsorship landscape.

Yes, the sponsorship finder works with both direct and transitive dependencies. It scans the full dependency tree of a given GitHub repository across multiple ecosystems to ensure no sponsorable dependencies are missed during the analysis.

Funding links for npm packages are verified using the deps.dev API, FUNDING.yml files, and native npm metadata. The tool cross-references these sources and validates the links before reporting sponsorship opportunities for your open source dependencies.