Verification Request: homebridge-petkit-bridge

[raulhartzen]

Plugin Name

homebridge-petkit-bridge

Link To GitHub Repo

https://github.com/raulhartzen/homebridge-petkit-bridge

Plugin Icon (Optional)

Companion plugin for petkit-bridge (https://github.com/raulhartzen/petkit-bridge), a self-hosted local HTTP bridge for PetKit devices. Unlike cloud-direct plugins, all PetKit cloud handling (session, auto re-login) lives in the bridge; the plugin stays thin, talks only to the local API, and keeps PetKit credentials off Homebridge entirely. Auto-discovers feeders, litter boxes and fountains as HomeKit accessories. Field-tested on Yumshare (dual hopper), Puramax 2 and Eversweet Max hardware.

The plugin does not offer the same nor less functionality than that of any existing verified plugin.

🟢 Yes

The plugin successfully installs and does not start unless it is configured.

🟢 Yes

The plugin does not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.

🟢 Yes

The plugin does not contain any analytics or calls that enable you to track the user.

🟢 Yes

If the plugin needs to write files to disk (cache, keys, etc.), it stores them inside the Homebridge storage directory.

🟢 Yes

The plugin does not throw unhandled exceptions, the plugin must catch and log its own errors.

🟢 Yes

More Information

Companion plugin for petkit-bridge (https://github.com/raulhartzen/petkit-bridge), a self-hosted local HTTP bridge for PetKit devices. Unlike cloud-direct plugins, all PetKit cloud handling (session management, automatic re-login on expiry) lives in the bridge; the plugin stays thin, talks only to the local token-protected API, and keeps PetKit credentials off Homebridge entirely. Devices are auto-discovered and exposed as HomeKit accessories (feeders, litter boxes, fountains). Field-tested on real hardware: Yumshare dual-hopper feeders, Puramax 2 litter box, Eversweet Max fountains. Release v0.2.0 (beta) with full changelog and release notes.

Plugin icon attached (original artwork, consistent with the project's banner — no third-party trademarks).

[github-actions]

🔴 Failed Checks

• Package JSON: keywords must include at least one of 'supports-hap' or 'supports-matter' — see Declaring Supported Transports
• Config Schema JSON: schema is invalid - required should not be a boolean property on individual fields. In JSON Schema, required must be an array at the object level listing required property names. Remove "required": true/false from individual properties and use "required": ["property1", "property2"] at the object level instead.
• Config Schema JSON: does not contain a name schema property

🟢 Passed Checks

• Installation: successfully installed
• Package JSON: homepage exists
• Package JSON: bugs.url exists and seems a valid URL
• Package JSON: keywords exist and contain 'homebridge-plugin'
• Package JSON: 'preinstall' in scripts is not present
• Package JSON: 'install' in scripts is not present
• Package JSON: 'postinstall' in scripts is not present
• Package JSON: engines.node property is compatible with Node 22
• Package JSON: engines.node property is compatible with Node 24
• Package JSON: engines.homebridge property is compatible with Homebridge 2.2.1
• Package JSON: initializer function found
• NPM Package: has not been deprecated
• GitHub Repo: version in package.json (v0.2.0) matches NPM version (v0.2.0)
• Config Schema JSON: exists and is valid JSON
• Config Schema JSON: contains a valid pluginAlias
• Config Schema JSON: pluginAlias matches the platform/accessory registered in code
• Config Schema JSON: the pluginType is set to 'platform'
• Dependencies: homebridge is not declared as a runtime/peer/bundled dependency
• Dependencies: hap-nodejs is not declared as a runtime/peer/bundled dependency
• Security: no known vulnerabilities in dependencies
• Security: code patterns flagged for manual review
• Security: no privilege escalation attempts detected
• GitHub Repo: repository is public
• GitHub Repo: repository is not archived
• GitHub Repo: issues are enabled
• GitHub Repo: contains releases

🔍 For Manual Review

The following items were detected and require manual review. We understand that these items may be false positives.

• Security: accesses environment files in config.schema.json

ℹ️ Check Details

• These checks were run against v0.2.0 of the plugin.
• Link to the run workflow: visit →.

📋 Next Steps

• Once you have fixed these failures, comment /check on this issue to run the checks again — your request will not move forward until the checks are re-run.
• If updating your package.json and config.schema.json files, don't forget to publish a new version to NPM.
• Remember this is an automatic script: if you think something has been marked as a failure in error, let us know with a reply.
• Feel free to ask any questions you have by replying to this issue.

[raulhartzen]

/check

Fixed in v0.2.1 (published to npm): added supports-hap keyword, converted required to a JSON Schema array at the object level, added the name platform property.

Note on the flagged manual-review item ("accesses environment files in config.schema.json"): the schema previously mentioned ".env" in a field description — documentation text about where the companion bridge stores its own configuration, not any file access by the plugin. Reworded in 0.2.1.

[github-actions]

🟢 Passed Checks

• Installation: successfully installed
• Package JSON: homepage exists
• Package JSON: bugs.url exists and seems a valid URL
• Package JSON: keywords exist and contain 'homebridge-plugin'
• Package JSON: keywords declare the supported transports ('supports-hap' and/or 'supports-matter')
• Package JSON: 'preinstall' in scripts is not present
• Package JSON: 'install' in scripts is not present
• Package JSON: 'postinstall' in scripts is not present
• Package JSON: engines.node property is compatible with Node 22
• Package JSON: engines.node property is compatible with Node 24
• Package JSON: engines.homebridge property is compatible with Homebridge 2.2.1
• Package JSON: initializer function found
• NPM Package: has not been deprecated
• GitHub Repo: version in package.json (v0.2.1) matches NPM version (v0.2.1)
• Config Schema JSON: exists and is valid JSON
• Config Schema JSON: contains valid JSON Schema
• Config Schema JSON: schema has valid type property
• Config Schema JSON: schema has valid properties for object type
• Config Schema JSON: contains a valid pluginAlias
• Config Schema JSON: pluginAlias matches the platform/accessory registered in code
• Config Schema JSON: the pluginType is set to 'platform'
• Config Schema JSON: contains a name schema property
• Dependencies: homebridge is not declared as a runtime/peer/bundled dependency
• Dependencies: hap-nodejs is not declared as a runtime/peer/bundled dependency
• Security: no known vulnerabilities in dependencies
• Security: no unsafe code patterns detected
• Security: no privilege escalation attempts detected
• Runtime: homebridge installed successfully
• Runtime: no config - homebridge should start without plugin configuration and plugin should not load
• Runtime: platform only - plugin should start with just platform property
• Runtime: minimal required - plugin should start with minimal required configuration
• Runtime: full config - plugin should start with comprehensive configuration
• Runtime: network resilience - plugin should handle network failures without crashing
• Runtime: plugin shuts down cleanly within 12s of SIGTERM
• Runtime: plugin restarts cleanly without port conflicts
• GitHub Repo: repository is public
• GitHub Repo: repository is not archived
• GitHub Repo: issues are enabled
• GitHub Repo: contains releases

ℹ️ Check Details

• These checks were run against v0.2.1 of the plugin.
• Link to the run workflow: visit →.
• External HTTP requests detected:
  • 📡 https://api.example.com/devices
    Methods: GET | Count: 3 | Scenarios: full config, minimal required, network resilience

📋 Next Steps

All checks passed successfully, nice work! Your plugin and/or icon will now be manually reviewed by the Homebridge team.