About

About Tavernary

Tavernary is a search and discovery catalog for AI roleplay tools in and around the SillyTavern community. It indexes public project information and directs visitors to each project's creator-owned repository or source page.

Why Tavernary exists

The tools people use to shape their roleplay experiences are spread across Reddit posts, Discord channels, creator repositories, and word of mouth. The best discoveries can be difficult to find again, and a great project can be invisible outside the small corner where someone happened to share it.

Tavernary gives that scattered community a shared place to gather: somewhere to explore what exists, understand what each project does, and follow the path back to the people who made it.

Built for exploration

Search for projects and creators, browse Frontends, Extensions, and System Presets, and use the catalog filters to narrow the field. Whether you are looking for a new interface, a small quality-of-life extension, or a preset to try, Tavernary is a place to start exploring.

Tavernary takes inspiration from PCPartPicker.com and from community knowledge shared on Reddit. Its goal is to bring fragmented knowledge into one place, then give people the tools to make something that fits them.

Make it yours with Kits

Kits are user-tailored collections of catalog projects. Browse community-made Kits for ideas, or assemble your own combination from the catalog instead of settling for one bundle chosen by Tavernary.

Reorder the stack, save a draft in your browser, share your Kit with others, and submit it for review. Kits let the community show how its tools fit together and help every visitor find a setup that feels like their own.

Projects remain independent

Tavernary links outward to creator-owned repositories and source pages. It does not host, mirror, redistribute, or maintain project files. Creators remain responsible for their own releases, documentation, licenses, and support.

If you have made something for the community, or know of a killer extension, prompt, or frontend that is not on Tavernary, you can add it to the catalog and help make the next discovery easier for someone else.

Adding Frontends

Frontends and Extensions require a public GitHub or Codeberg repository. The code must be visible without signing in, but an open-source license is not required. Tavernary does not require a popularity level or recent activity for inclusion.

A submission should be an identifiable, usable Frontend rather than a library, theme, mockup, or placeholder, with enough public documentation to understand what it is and how to run it.

Repositories from both providers receive the same activity, community, and attribution treatment in the catalog.

Safety and security

Tavernary is an independent directory of third-party projects. Listings are not endorsements, certifications, or guarantees of safety. Eligible GitHub listings may be scanned by TavernKeeper, an advisory security-scanning system, but scan results do not guarantee that a project is safe or free of harmful behavior. Tavernary does not host, install, or execute listed projects and cannot guarantee their code, dependencies, releases, installers, or behavior.

Review a project's repository, permissions, dependencies, release history, and credential handling before installing or using it. Never provide API keys, passwords, or other secrets to software unless you understand how they are used.

Scan colors describe the evidence at one exact commit. Teal means low concern, orange means a material concern, and red means immediate danger at the exact scanned commit. A critical dependency advisory alone does not make a project red. Red results identify credible malicious or compromised behavior, a critical and readily exploitable vulnerability, or both. Red projects remain listed so the community can see the warning; scan results do not automatically hide or delist a project.

Reporting and removal

A verified personal GitHub owner can use Update or rename your project listing to request a card edit, a move of the same repository, or a delist. For organization-owned repositories, rights concerns, and other listing problems, use Report a project listing.

Users can report inaccurate, outdated, unsafe, malicious, or abusive listings. This includes suspected malware or credential theft, hateful or discriminatory content, exploitative or non-consensual sexual content, sexual content involving minors, threats, or other clearly harmful material. Include the project URL, specific concern, and useful evidence. Do not include API keys, passwords, or other private information.

Security vulnerabilities should be reported through the repository's private security path. A listing report may result in a correction, warning, pause, or removal.