FiftyOne Plugins Catalogs Core, Example, and Community Extensions for the App

voxel51/fiftyone-plugins is not a single plugin to install. It is the curated index for FiftyOne’s plugin framework, grouping extensions by who maintains them and how they are meant to be used. For teams already working in the FiftyOne App, that distinction matters more than the number of entries: it signals what you can adopt directly, what to use as a reference implementation, and what to audit before putting in front of users. The framework itself is the point. According to the README, plugins can add functionality to the App, integrate with other tools and APIs, render custom panels, and add custom buttons to menus. With FiftyOne Teams, plugins can also expose delegated operations — long-running tasks that run on a connected compute cluster rather than in the browser session. That makes the catalog relevant to dataset curation, evaluation, and model workflows that need to stay inside the App instead of bouncing between separate utilities. How the catalog is organized The repository separates four tiers, which is a useful readiness signal on its own. Core plugins are maintained by the FiftyOne team and described as functionality most users will likely want, including annotation, Brain, dashboard, evaluation, import/export, indexes, plugin management, delegated operations, runs, utilities, and Zoo access for datasets and models. Voxel51 Plugins are non-core but officially maintained, covering MLflow