Contributing

ExtenSilica is built for reproducible RISC-V extension work. Useful contributions improve a real package: provenance, specifications, encodings, dependencies, artifacts, tests, examples, or documentation. Catalog volume alone is not a contribution.

• Scaffold with the Extension Wizard or xsil new, then publish with xsil publish.
• Set honest standardStatus, encoding, dependencies, and provenance; do not imply ratification or official endorsement without authority.
• Add a README on the Extension page and link your source repository when public.
• Use the Extension page Cite block (CFF + BibTeX) for papers and Zenodo deposits — see our Zenodo manual in the platform repository.

Package maintainers and community contributors can improve the technical archive without turning ExtenSilica into a separate porting framework:

• Update a specification, version, encoding, CSR range, or dependency
• Add reproducible simulator, toolchain, RTL, test, example, or hardware artifacts
• Correct provenance and claim maintenance of a package you control upstream
• Report duplicate, misleading, stale, or unverifiable metadata

Coordinate changes in the package's upstream repository or through the contact channels on its registry page. Published versions remain immutable; corrections ship as a new version.

If you maintain an upstream extension but do not yet own the registry listing, use the ownership-claim flow on the Extension page. Claims are reviewed by platform admins with evidence you control the work.

The registry web app, API, and tooling live in the ExtenSilica GitHub organization. Contributions to the platform repository require the Individual Contributor License Agreement (CLA) and are licensed under Apache-2.0 — see docs/CLA.md and CONTRIBUTING.md in the platform repository.

Report security-sensitive issues through the contact path in our Terms; do not open public issues for undisclosed vulnerabilities.

Verified engineering work that improves the extension catalog may earn XSIL governance tokens. Publishing empty or duplicate metadata earns nothing. Grants are reviewed according to the value, provenance, and reproducibility of the contribution; linking a wallet is optional and only used for on-chain claim when enabled.

Read Governance for stewardship boundaries and Adoption for public usage metrics used in foundation discussions.