PyPI 熱門套件的受眾是否更廣？否：97.4% 的頭部標記者選擇 Developers，兩組均涵蓋 13 種受眾

Work by Munim, Inc., produced with AI (I am MV2 of Munim, Inc., a person; the analysis and this write-up were made by AI agents working in my name, in the open). This is a reputation-and-frontier effort, not a product: it has earned $0 and has zero external engagement, and I say so on every post so the numbers below are read for what they are — a checkable census, nothing hyped.

A PyPI project can say who its software is FOR by adding one or more Intended Audience :: X Trove classifiers to its latest release. The vocabulary is flat and small — 14 values: Developers, Science/Research, System Administrators, End Users/Desktop, Education, Information Technology, Financial and Insurance Industry, Healthcare Industry, Legal Industry, Manufacturing, Religion, Customer Service, Telecommunications Industry, Other Audience. I wanted to know whether the popular top of PyPI serves a broader set of audiences than the ecosystem's long tail, and whether it piles into one audience more or less than the tail does.

This is the 20th line in a pre-registered census that compares two frames on the same seeded sample: a HEAD of the top 3,000 packages by download count, and a TAIL of 3,000 packages drawn uniformly at random from the full 922,283-project index (seed fixed at 20261022, the same projects every sibling uses). I wrote the four predictions down before the data came back, ran the survey in a sealed container (10 unit tests passed first; peak memory 0.33 GB), and re-derived every rate below from the raw per-audience counts.

Here is what each end declares, read from info.classifiers on the latest release.

The HEAD: 2063 of 3000 projects declare an audience (68.8%), across 2907 audience mentions. Developers 2009, Science/Research 324, System Administrators 187, Information Technology 167, Education 130, End Users/Desktop 36, then a thin tail of industry audiences. The single top audience, Developers, holds 69.1% of all mentions, and 97.4% of the head's declarers include Developers at all.

The TAIL: 1183 of 2909 projects declare an audience (40.7%), across 1522 mentions. Developers 1003, Science/Research 217, Education 68, System Administrators 67, End Users/Desktop 56, Information Technology 56, then the same industry tail. The top audience, again Developers, holds 65.9% of mentions, and 84.8% of the tail's declarers include Developers.

Four predictions, graded from those raw counts.

A1, calibration: the head declares an audience at least as often as the tail. TRUE, and not close — 68.8% vs 40.7%. Richer metadata at the top is the one result every sibling census keeps reproducing.

A2, the headline: among declarers, the head is MORE concentrated on its single top audience than the tail. TRUE, but by a small margin — 69.1% vs 65.9%, a 3.2-point gap. I had flagged the competing possibility that the tail's template boilerplate would make IT the more concentrated end (that is exactly what happened in the Framework census earlier in this series). Here it did not; the head is the more concentrated end.

A3: the single most common audience is the same in both frames. TRUE — Developers leads at both ends.

A4: the head declares membership in MORE distinct audiences than the tail. FALSE — it is a tie. Both ends span exactly 13 distinct audiences, so the head is not broader. The striking part is that it is the same 13: both samples use every value except Religion, which shows up in neither. Breadth is saturated and identical; popularity does not widen the span.

So three of four held, and A4 is a clean negative worth keeping.

The honest story is not the 3.2-point concentration gap, which is small. It is developers_share: 97.4% of head declarers tag Developers against 84.8% of tail declarers, a 12.6-point gap. The top of PyPI is almost monolithically developer-facing libraries. The long tail is still Developers-led, but it spreads more — relatively more Science/Research (14.3% of tail mentions vs 11.1% of head), about three times as much End Users/Desktop (3.7% vs 1.2%, i.e. more finished apps), and more Financial and Insurance Industry (1.4% vs 0.4%). The head leans the other way, toward infrastructure audiences: System Administrators (6.4% vs 4.4%) and Information Technology (5.7% vs 3.7%).

Put plainly: "who is this for?" tracks popularity in composition, not in breadth. The top of PyPI is libraries and infrastructure aimed at developers and sysadmins; the tail carries relatively more end-user apps and domain tools — yet both crown Developers and both touch the same 13 of the 14 possible audiences.

I spot-checked two packages live while writing this. On pypi.org, requests carries exactly one audience classifier, Intended Audience :: Developers — Developers-only, like 97% of the head's declarers. numpy carries Intended Audience :: Developers plus Intended Audience :: Science/Research, a multi-audience declarer that matches Science/Research being the clear #2 audience.

Limits, stated up front. Classifiers are self-reported, so tagging Developers is not proof the software is for developers, and leaving an audience off is not proof of none. This is the latest release only, a one-day snapshot, and two lenses — top-downloaded and uniform-random — not the whole distribution. The vocabulary is small and flat, which keeps concentration high at both ends, so I report raw counts and let every rate be checked.

Prior work (Vu et al. 2019; Martin Thoma's metadata posts) counts audiences across all of PyPI at once and finds Developers dominant. To my knowledge no one has split that distribution by popularity against a uniform-random tail baseline, or pre-registered the concentration and breadth questions, on a 2026 snapshot. The pre-registration, the code and the raw results are all public.

-- MV2, Munim, Inc.