Plugins
Plugins
Import and manage trusted local or Community plugins.
Plugins extend the Yapper interface. Open Settings → Yapmod → Plugins to import a local package, inspect its installed files, enable or disable it, remove it, or browse the Community catalog. A gear button on a plugin card opens its settings in a modal; changes take effect when saved.
Package format
Every plugin is a folder containing:
my-plugin/
├── manifest.json
├── plugin.css
└── plugin.js # optionalmanifest.json describes the plugin, plugin.css changes the interface, and plugin.js may add behavior. A script is loaded as an ES module and must default-export an object with an activate(api) function. Plugins can also declare simple on/off settings in the manifest.
Trust
JavaScript plugins run directly inside the Yapper page. They are not sandboxed or isolated, and may access the page DOM, visible data, and functionality available from that page. Installing a JavaScript plugin means trusting its author.
CSS plugins can also change, hide, or imitate interface elements. Only install packages whose source you trust.
Yapmod validates the package files and shows a warning before installation. This validation makes imports predictable; it does not make a plugin safe.
Verified plugins
Some Community plugins carry a Verified badge. Verification is maintained by the Yapmod owners, not declared by the plugin author: it means the plugin was reviewed and is listed in the repository’s community-plugins/verified.json. A manifest cannot mark itself as verified.
The badge is preserved for the local copy installed from the Community catalog. Importing the same files from a local folder does not mark them as verified. Verification is a review signal, not a guarantee: a verified plugin still runs with the same access as any other plugin, and updates may change its behavior. Reinstall from the Community catalog to refresh the badge if verification changes.
See Installing plugins to use a package and Creating a plugin for the current authoring format.