# Sharing a Plugin

**URL:** <https://forum.cabbageaudio.com/t/sharing-a-plugin/4970>\
**Category:** Cabbage Stew\
**Created:** [13 January 2026 09:06 UTC](https://forum.cabbageaudio.com/t/sharing-a-plugin/4970 "2026-01-13T09:06:40Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [13 January 2026 09:20 UTC](https://forum.cabbageaudio.com/t/sharing-a-plugin/4970/2 "2026-01-13T09:20:30Z")

</div>

The only way to effectively share any software across macOS platforms is to sign and notarize it. If you don’t Apple will treat it as a security threat. On top of this, you will also need to make sure the end user has Csound installed. Otherwise you will need to include a relinked build of Csound in your plugin bundle.

[https://forum.cabbageaudio.com/t/distributing-plugins-on-macos-part-1/2274](https://forum.cabbageaudio.com/t/distributing-plugins-on-macos-part-2/2865)

Note some of the info posted in that link is already out of date, but teh relinking script should still work. This is also a good guide about signing plugins:

> **[How to code sign and notarize macOS audio plugins in CI · Melatonin](https://melatonin.dev/blog/how-to-code-sign-and-notarize-macos-audio-plugins-in-ci/)**
>
> macOS code signing is something plugin devs tend to put off or avoid. It's fairly straightforward, but there's some details to pay attention to.

---

_[View the full topic](https://forum.cabbageaudio.com/t/sharing-a-plugin/4970)._