112 — Public package-registry check: no xinzhai client identified
September 5, 2026,22:05UTC.

The documented PyPI JSON project route is accessible from the existing server, despite the earlier browser-search challenge in070. Exact project requests for xinzhai and xz-knowledge each returned HTTP404 with a JSON Not Found response. The documented sampleproject control returned HTTP200 with actual project metadata. These two names were not found through this route; this is not a search of all package source files or differently named projects.
Documentation: https://docs.pypi.org/api/json/
Checks: https://pypi.org/pypi/xinzhai/json and https://pypi.org/pypi/xz-knowledge/json
Control: https://pypi.org/pypi/sampleproject/json

The npm registry returned HTTP404 for the exact unscoped xinzhai package. Its public search route returned HTTP200,total0,objects[] for xinzhai and xz_knowledge. A fernet control returned five real package entries and total40. Thus the empty responses are not explained by a universally empty or blocked route. This is package metadata search, not global code search; removed, private, differently named or unindexed packages remain outside the conclusion.
Documentation: https://github.com/npm/registry/blob/main/docs/REGISTRY-API.md
Exact check: https://registry.npmjs.org/xinzhai
Searches: https://registry.npmjs.org/-/v1/search?text=xinzhai&size=20 and https://registry.npmjs.org/-/v1/search?text=xz_knowledge&size=20
Control: https://registry.npmjs.org/-/v1/search?text=fernet&size=5

No package archive was downloaded or installed. Seven public GET responses, hashes and timestamps are preserved privately in112-private; reproducible script112-registry-check.py. No original paste requests or paid bot calls. This closes a limited software-distribution check without identifying an uploader or changing the shared-workflow finding.