펫 카탈로그에 멋진 기능을 더해 보세요
Spotify, 캘린더, 집중, 게임, AI 도우미나 작은 데스크톱 습관 아이디어가 있나요? 공개 GitHub 저장소에서 만들고 리뷰를 요청하면, 안전하게 패키징된 버전을 OpenPets 사용자에게 제공할 수 있습니다.
Starter repo
Clone a complete example first
The starter repo includes a manifest, JavaScript entry, locale file, bundled SVG icon, README, and SDK smoke test. You can test it alone, then load that folder from OpenPets → Plugins → Developer Mode.
플러그인 만들기
매니페스트, JavaScript 엔트리 파일, 로케일, 번들 에셋을 준비합니다.
릴리스 태그 만들기
리뷰어가 정확한 소스를 고정할 수 있도록 GitHub 태그나 커밋을 공개합니다.
안전하게 카탈로그 등록
OpenPets는 카탈로그에 표시하기 전에 권한, 호스트, 에셋, 패키징을 검토합니다.
Submission readiness
A practical pre-submit flow
Work through these checks before opening an issue. Consult the
1. Confirm the manifest
Keep openpets.plugin.json alongside the entry file, with a stable plugin id, semver version, declared entry, and any bundled assets.
2. Declare only what you use
Request minimal permissions. If the plugin uses network access, declare only the exact public HTTPS hosts it needs.
3. Make the build reproducible
Validate and test the standalone plugin folder, then pin the submitted source with an immutable Git tag or full commit SHA.
4. Explain the purpose
Write a short README covering what the plugin does, local testing, and any account, API key, or OAuth setup users need.
5. Assemble the review packet
Include the plugin name and id, repository and subdirectory, pinned source, requested permissions and hosts with their purpose, plus external setup.
What to prepare
- A public GitHub repository with your plugin source.
- A plugin folder containing openpets.plugin.json, index.js, locales/en.json, and declared assets.
- A stable plugin id, semver version, minimal permissions, and exact network hosts.
- A Git tag or full commit SHA that reviewers can pin.
- A short README explaining what the plugin does and how users set it up.
Review packet
- Plugin name and plugin id.
- GitHub repo URL and plugin subdirectory.
- Release tag or commit SHA.
- Requested permissions and why each one is needed.
- Network hosts and what each host is used for.
- Any external account setup users need, such as OAuth app setup.
Copy into the GitHub issue if you are not using the form fields
Plugin name:
Plugin id:
GitHub repo URL:
Plugin subdirectory: .
Release tag or commit SHA:
Requested permissions:
- permission-name: why it is needed
Network hosts:
- host.example.com: what it is used for
External account setup:
- None, or explain OAuth/API setup users must complete