Verification Request: homebridge-bravia

[normen]

Plugin Name

homebridge-bravia

Link To GitHub Repo

https://github.com/normen/homebridge-bravia

Plugin Info

The plugin was verified but lost the badge (dunno why) - its HB 2.0 compatible and all that jazz now.

[github-actions]

🔴 Failed Checks

• Config Schema JSON: schema missing type property
• Config Schema JSON: does not contain a name schema property
• Dependencies: homebridge was installed as a dependency
• Dependencies: hap-nodejs was installed as a dependency
• GitHub Repo: should contain releases

🟢 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.node property is compatible with Node 24
• Package JSON: engines.homebridge property is compatible with Homebridge 1.11.4
• Package JSON: initializer function found
• NPM Package: has not been deprecated
• GitHub Repo: version in package.json (v2.5.0) matches NPM version (v2.5.0)
• Config Schema JSON: exists and is valid JSON
• Config Schema JSON: contains valid JSON Schema
• Config Schema JSON: contains a valid pluginAlias
• Config Schema JSON: the pluginType is set to 'platform'
• 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

ℹ️ Check Details

• These checks were run against v2.5.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.

[normen]

/check

[github-actions]

🔴 Failed Checks

• GitHub Repo: should contain releases

🟢 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.node property is compatible with Node 24
• Package JSON: engines.homebridge property is compatible with Homebridge 1.11.4
• Package JSON: initializer function found
• NPM Package: has not been deprecated
• GitHub Repo: version in package.json (v2.5.1) matches NPM version (v2.5.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: 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

ℹ️ Check Details

• These checks were run against v2.5.1 of the plugin.
• Link to the run workflow: visit →.
• External HTTP requests detected:
  • 📡 http://test-value:8080/sony/accessControl/
    Methods: POST | Count: 2 | Scenarios: full config, network resilience
  • 📡 http://test-value:8080/sony/avContent/
    Methods: POST | Count: 10 | Scenarios: full config, network resilience
  • 📡 http://test-value:8080/sony/system/
    Methods: POST | Count: 10 | Scenarios: full config, network resilience

📋 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.

[normen]

I don't want to create releases.

[normen]

/check