Skip to content

Verification Request: homebridge-tuya-platform #875

New issue
New issue
Closed
Closed
Verification Request: homebridge-tuya-platform#875
Labels
request-verificationverifieduse when a plugin meets the criteria - adds the verified badge text

Description

@tassy-h
tassy-h
opened on Sep 21, 2025

Plugin Name

@tassy-h/homebridge-tuya-platform

Link To GitHub Repo

https://github.com/tassy-h/homebridge-tuya-platform

Plugin Icon (Optional)

No response

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

No response

Activity

  1. tassy-h
    added
    pendingthe label given to a new verification/icon request
    request-verification
    on Sep 21, 2025

  2. github-actions commented on Sep 21, 2025

    @github-actions
    github-actionsBot
    on Sep 21, 2025 – with GitHub Actions
    Contributor

    🔴 Failed Checks

    • 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.
    • Security: potentially unsafe code patterns found in: test/util.ts
    • Runtime: skipped due to prior test failures

    🟢 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 20
    • Package JSON: engines.node property is compatible with Node 22
    • Package JSON: engines.homebridge property is compatible with Homebridge 1.11.0
    • Package JSON: initializer function found
    • NPM Package: has not been deprecated
    • GitHub Repo: version in package.json (v2.0.1-beta.0) matches NPM version (v2.0.1-beta.0)
    • Config Schema JSON: exists and is valid JSON
    • Config Schema JSON: contains a valid pluginAlias
    • Config Schema JSON: the pluginType is set to 'platform'
    • Config Schema JSON: contains a name schema property
    • Dependencies: homebridge was not installed as a dependency
    • Dependencies: hap-nodejs was not installed as a dependency
    • Security: no known vulnerabilities in dependencies
    • 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

    ℹ️ Check Details

    • These checks were run against v2.0.1-beta.0 of the plugin.
    • Link to the run workflow: visit →.

    📋 Next Steps

    • Please action these failures and then comment /check to run the checks again.
    • 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.
  3. github-actions
    added
    awaiting-changesuse after review has started - awaiting user to make changes to plugin
    and removed
    pendingthe label given to a new verification/icon request
    on Sep 21, 2025

  4. tassy-h commented on Sep 21, 2025

    @tassy-h
    tassy-h
    on Sep 21, 2025
    Author

    /check

  5. github-actions
    added
    pendingthe label given to a new verification/icon request
    and removed
    awaiting-changesuse after review has started - awaiting user to make changes to plugin
    on Sep 21, 2025

  6. github-actions commented on Sep 21, 2025

    @github-actions
    github-actionsBot
    on Sep 21, 2025 – with GitHub Actions
    Contributor

    🔴 Failed Checks

    • GitHub Repo: version mismatch - NPM has v2.0.1-beta.0 but GitHub package.json has v2.0.2-beta.0
    • 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.
    • Security: potentially unsafe code patterns found in: test/util.ts
    • Runtime: skipped due to prior test failures

    🟢 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 20
    • Package JSON: engines.node property is compatible with Node 22
    • Package JSON: engines.homebridge property is compatible with Homebridge 1.11.0
    • Package JSON: initializer function found
    • NPM Package: has not been deprecated
    • Config Schema JSON: exists and is valid JSON
    • Config Schema JSON: contains a valid pluginAlias
    • Config Schema JSON: the pluginType is set to 'platform'
    • Config Schema JSON: contains a name schema property
    • Dependencies: homebridge was not installed as a dependency
    • Dependencies: hap-nodejs was not installed as a dependency
    • Security: no known vulnerabilities in dependencies
    • 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

    ℹ️ Check Details

    • These checks were run against v2.0.1-beta.0 of the plugin.
    • Link to the run workflow: visit →.

    📋 Next Steps

    • Please action these failures and then comment /check to run the checks again.
    • 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.
  7. github-actions
    added
    awaiting-changesuse after review has started - awaiting user to make changes to plugin
    and removed
    pendingthe label given to a new verification/icon request
    on Sep 21, 2025

  8. tassy-h commented on Sep 21, 2025

    @tassy-h
    tassy-h
    on Sep 21, 2025
    Author

    /check

  9. github-actions
    added
    pendingthe label given to a new verification/icon request
    and removed
    awaiting-changesuse after review has started - awaiting user to make changes to plugin
    on Sep 21, 2025

  10. github-actions commented on Sep 21, 2025

    @github-actions
    github-actionsBot
    on Sep 21, 2025 – with GitHub Actions
    Contributor

    🔴 Failed Checks

    • 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.
    • Security: potentially unsafe code patterns found in: test/util.ts
    • Runtime: skipped due to prior test failures

    🟢 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 20
    • Package JSON: engines.node property is compatible with Node 22
    • Package JSON: engines.homebridge property is compatible with Homebridge 1.11.0
    • Package JSON: initializer function found
    • NPM Package: has not been deprecated
    • GitHub Repo: version in package.json (v2.0.2-beta.0) matches NPM version (v2.0.2-beta.0)
    • Config Schema JSON: exists and is valid JSON
    • Config Schema JSON: contains a valid pluginAlias
    • Config Schema JSON: the pluginType is set to 'platform'
    • Config Schema JSON: contains a name schema property
    • Dependencies: homebridge was not installed as a dependency
    • Dependencies: hap-nodejs was not installed as a dependency
    • Security: no known vulnerabilities in dependencies
    • 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

    ℹ️ Check Details

    • These checks were run against v2.0.2-beta.0 of the plugin.
    • Link to the run workflow: visit →.

    📋 Next Steps

    • Please action these failures and then comment /check to run the checks again.
    • 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.

  11. 16 remaining items

  12. github-actions
    removed
    awaiting-changesuse after review has started - awaiting user to make changes to plugin
    on Sep 22, 2025

  13. github-actions commented on Sep 22, 2025

    @github-actions
    github-actionsBot
    on Sep 22, 2025 – with GitHub Actions
    Contributor

    🟢 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 20
    • Package JSON: engines.node property is compatible with Node 22
    • Package JSON: engines.homebridge property is compatible with Homebridge 1.11.0
    • Package JSON: initializer function found
    • NPM Package: has not been deprecated
    • GitHub Repo: version in package.json (v2.0.2-beta.1) matches NPM version (v2.0.2-beta.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: the pluginType is set to 'platform'
    • Config Schema JSON: contains a name schema property
    • Dependencies: homebridge was not installed as a dependency
    • Dependencies: hap-nodejs was not installed as a dependency
    • Security: no known vulnerabilities in dependencies
    • Security: code patterns flagged for manual review
    • 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
    • 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 test/util.ts

    ℹ️ Check Details

    • These checks were run against v2.0.2-beta.1 of the plugin.
    • Link to the run workflow: visit →.
    • External HTTP requests detected:
      • 📡 https://api.example.com/v1.0/iot-01/associated-users/actions/authorized-login
        Methods: post | Count: 18 | Scenarios: full config, network resilience

    📋 Next Steps

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

  14. github-actions
    added
    awaiting-final-review
    and removed
    pendingthe label given to a new verification/icon request
    on Sep 22, 2025

  15. bwp91 commented on Sep 22, 2025

    @bwp91
    bwp91
    on Sep 22, 2025
    Contributor

    @tassy-h would you be interested at all in making this a scoped plugin? Please see for info:

  16. tassy-h commented on Sep 22, 2025

    @tassy-h
    tassy-h
    on Sep 22, 2025
    Author

    @tassy-h would you be interested at all in making this a scoped plugin? Please see for info:

    Hi! @bwp91
    From a user's perspective, I found the scoped plugin is very meaningful.
    However, since this is a forked project, I don't fully understand the code.
    Additionally, I'm not very familiar with GitHub or npm development. Is that okay?

  17. bwp91 commented on Sep 22, 2025

    @bwp91
    bwp91
    on Sep 22, 2025
    Contributor

    @tassy-h are you on the homebridge discord server or would you be happy to message on there in a private chat?

    https://discord.gg/kqNCe2D

    my username there is bwp91.

  18. bwp91
    added a commit that references this issue on Sep 27, 2025

    verify: homebridge-plugins/homebridge-tuya

    4c1a51f
  19. bwp91
    added
    verifieduse when a plugin meets the criteria - adds the verified badge text
    and removed
    awaiting-final-review
    on Sep 27, 2025
  20. bwp91
    closed this as completedon Sep 27, 2025

  21. github-actions commented on Sep 27, 2025

    @github-actions
    github-actionsBot
    on Sep 27, 2025 – with GitHub Actions
    Contributor

    Congratulations! Your plugin has been verified!

    You can now add one of the Verified by Homebridge badges to your plugin's README:

    verified-by-homebridge

    [![verified-by-homebridge](https://badgen.net/badge/homebridge/verified/purple)](https://github.com/homebridge/homebridge/wiki/Verified-Plugins)

    verified-by-homebridge

    [![verified-by-homebridge](https://img.shields.io/badge/homebridge-verified-blueviolet?color=%23491F59&style=for-the-badge&logoColor=%23FFFFFF&logo=homebridge)](https://github.com/homebridge/homebridge/wiki/Verified-Plugins)

    Your plugin is now also eligible to display a ❤️ Donate button on its tile in the Homebridge UI. See https://github.com/homebridge/homebridge/wiki/Donation-Links for instructions.

    Interested in getting a @homebridge-plugins/ scope for your plugin? See our Homebridge Scoped Plugins program.

    If for any reason in the future you can no longer maintain your plugin, please consider transferring it to our Homebridge Plugins organization.

    Don't forget to join the official Homebridge Discord server, where plugin developers can get tips and advice from other developers and the Homebridge project team in the #plugin-development channel!

    As a verified plugin, you can request a channel in the Discord server to discuss your plugin with users and other developers. Just ask in the #plugin-development channel.

    Thank you for your contribution to the Homebridge community.

    • The Homebridge Team
  22. github-actions
    reopened this on Sep 27, 2025
  23. tassy-h
    added a commit that references this issue on Sep 27, 2025

    homebridge verified

    dd66b06
  24. bwp91
    closed this as completedon Sep 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    request-verificationverifieduse when a plugin meets the criteria - adds the verified badge text

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions