Contributing

ExtenSilica is built for reproducible RISC-V extension work. Contribution is measured by useful packages, verified implementations, public profiles, and citable artifacts — not by payments processed on this site.

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

Package maintainers and the community can open implementation requests to coordinate porting, tests, or verification work:

• Express interest with your public implementer profile
• Submit work and record verification runs
• Optional funding-contact fields are off-platform only — the registry does not hold funds or broker contracts

Build reputation via your /users/<username> page and verified submissions.

If you maintain an upstream extension but do not yet own the registry listing, use the ownership-claim flow on the package 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.

Eligible registry work may earn XSIL governance points. Grants are reviewed before they count toward your balance; 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.