# Community plugins and adapters (/docs/v/0.6.1/plugins/community)



Third-party adapters and plugins are npm packages listed in a static registry maintained in this repository by pull request. Browse here; build and publish with the [authoring guides](/docs/v/0.6.1/guides/authoring/publish-community-plugin).

<CommunityPluginRegistry />

## What gets listed [#what-gets-listed]

| Kind    | What the package adds                            | Typical setup                       |
| ------- | ------------------------------------------------ | ----------------------------------- |
| Adapter | A provider implementation for one email service. | `plugins: [acmeMail({ apiKey })]`   |
| Plugin  | Reusable send behavior, policy, or helpers.      | `plugins: [requireMetadata("key")]` |
| Hybrid  | Both a provider and behavior in one package.     | `plugins: [providerWithDefaults()]` |

Adapter packages are mounted through `plugins` too — the plugin wrapper registers the provider in one call. See [Writing plugins](/docs/v/0.6.1/plugins/writing-plugins#register-adapters).

## Labels [#labels]

| Label     | Meaning                                                                   |
| --------- | ------------------------------------------------------------------------- |
| Community | Listed by pull request. Not endorsed or reviewed beyond the entry checks. |
| Verified  | Passed the registry's static checks for a specific package version.       |
| Official  | Maintained by OpenCore or in this repository.                             |

Verified is not a security review — the exact checks and the entry schema are documented in the [community registry reference](/docs/v/0.6.1/reference/community-registry).

## List your package [#list-your-package]

1. Build and publish to npm — follow [Publish a community adapter](/docs/v/0.6.1/guides/authoring/publish-community-adapter) for provider packages or [Publish a community plugin](/docs/v/0.6.1/guides/authoring/publish-community-plugin) for behavior packages.
2. Open a pull request adding an entry to `apps/fumadocs/content/community/plugins.json` (shape in the [registry reference](/docs/v/0.6.1/reference/community-registry)).
3. Want feedback first? Open the `Community package listing` issue template with your package and source links.