Only npm Offers Structured Funding Data; PyPI and crates.io Fall Short

A developer who maintains a tool for normalizing package metadata across npm, PyPI, and crates.io tested whether each registry's public API could reliably surface funding information for open-source maintainers. npm proved the most capable, with a formal 'funding' field in package.json and a dedicated CLI command, though only 36% of 25 tested packages used it and the data format was inconsistent. PyPI relies on free-form, manually entered project URLs with no reserved funding key, forcing developers to guess at labels like 'Funding', 'Donate', or 'Sponsor' — making any automated lookup a fragile heuristic. crates.io's sparse index, the format cargo reads during dependency resolution, lacks even basic homepage or repository fields, leaving funding discovery essentially impossible through the API alone. The findings highlight a structural gap in open-source infrastructure at a time when maintainer burnout and supply-chain vulnerabilities have made funding sustainability a pressing industry concern.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in