Skip to content
プロジェクト

SteamDeckHomebrew/decky-plugin-database

GitHubで見る

SteamDeckHomebrew/decky-plugin-database has 355 GitHub stars and 274 forks. GitHot measured 0 stars in 24 hours and 0 in 7 days. Last checked 2026-11-20 14:35 UTC. Last push 2026-11-16.

この数値の測り方

計測したスター増加

24時間
0
7日間
0
15日間
履歴を収集中
1か月
履歴を収集中

期間ごとの純増数です。期間は重複しており、日別の値ではありません。未計測の値は空欄です。スター数は注目度の指標であり、品質の保証ではありません。

概要

Decky Plugin Database. PR your plugins to this repository to have them added to the store!

データ

Decky Plugin Database Chat

This repository exists solely for developers to submit plugins

Use the built-in Plugin Store to download and install plugins.

Submit your plugin

For plugin developers submitting their plugin for the first time, please consult the wiki page on submitting your plugin. This README provides a good resource for the simple git related and a few other items, but the wiki has the rest of the information you'll need.

To submit a plugin to Decky's plugin store, open a pull request adding your plugin as a submodule (take a look at #189 for example). Don't forget to bump your version number in package.json. If you are not sure how to make a submodule, please reference the git docs on submodules.

Once you have your submodule added, in order to update it to a newer version:

  1. git checkout main (ensure you are in sync with upstream from your fork and pull)
  2. git checkout -b update/your-plugin (or whatever you like to call it)
  3. cd plugins/your-plugin
  4. git pull
  5. cd ../..
  6. git add plugins/your-plugin
  7. git commit -m "your commit message"
  8. git push

Testing Other's Plugins

While not required, testing other developers' plugins can help the community and may prioritize your own pull request. If you choose to participate in community testing, you can follow the testing guide to learn how to test other plugins and provide valuable feedback.

You can easily track PRs that are ready for review in this view: SDH Tracker

Please make sure your plugin is compliant with the pull-request template's steps. Plugins found to be out of compliance will not be accepted. If your plugin does not meet any of the criteria for utilizing a custom backend, then it only requires testing against Stable and Beta SteamOS Update Channels.