Schema library developer-ecosystem
Structure repository and package metadata.
Use these schemas to normalize public GitHub repository and package-registry pages into records for dependency, adoption, and ecosystem analysis.
Records
Choose the record your workflow expects.
GitHub Repository
GitHub repository data for OSS research and competitive intel.
owner · repo_name · full_name · /extract/json
Package Registry Entry
Package from npm, PyPI, crates.io, etc.
registry · package_name · package_version · /extract/json
How to use one
Four steps from a schema to a validated object.
Pick the record type
Choose the object closest to what your next step expects.
Inspect and adapt the fields
Drop what you do not need and describe anything ambiguous.
Send it with a public URL
The schema and the source page go to Extract together.
Validate what returns
Check the object in your application before writing it anywhere.
Extract or Generate
When to use Generate instead.
- Does the page state the fields? Extract is the call.
- Does the output need classification, comparison or inference? Generate returns that in your schema.