Publish extensions
Share a plugin or theme, wire it to GitHub releases, and let the audit pipeline produce a public trail for each version.
Read the publishing guide →Community Open source Early by design
Help make em—dash useful.
The marketplace is young. The useful work is practical and public: publish extensions, improve docs, test installs, review trust signals, and leave clearer trails for the next person.
Contribution paths.
Pick the work closest to what you already know. The project needs authors, readers, reviewers, testers, and people who can make rough edges legible.
Improve the docs
Tighten the Learn pages, contributor guide, manifest reference, and install notes so the next developer can move faster.
Open a docs issue →Test real installs
Run marketplace plugins in an EmDash site, check capability prompts, and report unclear install or consent behaviour.
Start with the install guide →Review trust signals
Read audit findings, inspect bundles, and suggest scanner rules when a pattern should block or caution a release.
Review the security policy →Moderate the catalog
Help handle reports, deprecations, author bans, and public tombstones with a bias toward clarity and due process.
Read the moderator guide →Build the marketplace
Work on the open-source registry itself: search, feeds, badges, API contracts, dashboards, and Cloudflare deployment.
Browse the repository →How the project works today.
- 01
No private roadmap theatre
Work starts in public issues or pull requests. If a decision affects authors or site owners, it should leave a public explanation.
- 02
Small patches count
A useful rejection message, a clearer manifest example, or a verified install note is real contribution work.
- 03
Trust over volume
The marketplace should grow at the speed it can review. A smaller catalog with honest signals is better than a large one people cannot trust.
Keep it useful, keep it kind.
A marketplace only works when people trust the catalog and trust each other enough to contribute. The same standards apply in issues, listings, reviews, dashboard metadata, and reports.
Code of conduct
The baseline for behaviour across the project.
Report a listing
Open a listing page to flag security, abuse, impersonation, licensing, or quality concerns.
Report community issue
Flag Code of Conduct, impersonation, or moderation concerns that are not tied to one listing.
Support
Find the right route for install issues, plugin questions, publisher help, and project bugs.
Transparency
Weekly public counts for reports, audit outcomes, and catalog health.
Weekly digest
A permanent archive of what changed in the ecosystem.