Independent plugins for Jellyfin 12, with shared release tooling and one Plugin Repository
Jellyfin plus sin, a little temptation for your media server; said JELLY-sin
JellySin provides independent plugins for Jellyfin 12, backed by shared release tooling and a single Plugin Repository. Each plugin owns its code and release cycle, while sharing common engineering principles, reproducible release packaging, and automated governance.
A Jellyfin server gains a feature without a fork: one plugin, one repository, one install source. Development happens in public, and the shared release automation builds reproducible packages, verifies each release and updates the Plugin Repository.
Plugin Repository URL for approved plugin releases:
https://raw.githubusercontent.com/jellysin/repo/main/manifest.json
Plugins appear after their first approved release.
JellySin coordinates plugin development, packaging, and distribution across dedicated repositories:
- Last.fm: music listening, favourites, metadata and discovery integration, currently in development.
- Release helper: reproducible packages, verified releases and Plugin Repository updates.
- Plugin Repository: one installation source for JellySin plugins.
- Engineering principles: baseline rules for small, bounded implementations, error handling, performance, and accessibility.
- Release helper documentation: shared release automation and manifest generation workflows.
Development happens in public. Read CONTRIBUTING.md before proposing changes. Contributions follow topic branches, pull requests with Conventional Commit titles, and squash merges.
Plugins appear after their first approved release:
- Last.fm integration: in development (plugin-lastfm).
- Release pipeline: automated via release-please and Release helper. See the Releases page and track version history in CHANGELOG.md.
JellySin builds independent plugins targeting Jellyfin 12.
New source code is licensed under the European Union Public Licence 1.2 (EUPL-1.2).
JellySin repositories adhere to declared engineering standards:
- HISS-21: High-Integrity Software Standards covering control flow, error handling, bounded loops, and deterministic execution (AGENTS.md).
- NASA/JPL Power of 10: structural rules for safety-critical, bounded code (principles).
- Conventional Commits: specification for commit messages paired with release-please automation (CONTRIBUTING.md).