Verification Request: homebridge-blink-security

[BitWise-0x]

Plugin Name

@jackietreeh0rn/homebridge-blink-security

Link To GitHub Repo

https://github.com/BitWise-0x/homebridge-blink-security

Plugin Icon (Optional)

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

you have an existing plugin for blink cameras verified, however, that plugin is completely broken: new users can't even log in since Blink killed the grant_type: password endpoint in late 2025. Open issues confirm this with 18+ comments and zero maintainer response. It also lacks doorbell, siren, night vision, record clip, and modern camera support.

My plugin provides substantial additional functionality on top of actually working:

Working auth (OAuth v2 + PKCE)
Doorbell support with press detection
Siren control
IMMI streaming protocol for all camera types (not just Gen1)
Night vision, record clip, privacy mode switches
Support for Mini 2, Wired Floodlight, and newer hardware

[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: '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.2
• Package JSON: initializer function found
• NPM Package: has not been deprecated
• GitHub Repo: version in package.json (v1.0.3) matches NPM version (v1.0.3)
• 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 src/accessories/cameraDelegate.ts

ℹ️ Check Details

• These checks were run against v1.0.3 of the plugin.
• Link to the run workflow: visit →.
• External HTTP requests detected:
  • 📡 https://api.oauth.blink.com/oauth/v2/authorize
    Methods: GET | Count: 3 | Scenarios: full config, minimal required, network resilience
  • 📡 https://api.oauth.blink.com/oauth/v2/signin
    Methods: GET, POST | Count: 4 | Scenarios: full config, minimal required

📋 Next Steps

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

[bwp91]

Hi @BitWise-0x

Would you be interested in using your plugin to create a scoped version with the homebridge plugins namespace, so your plugin would be @homebridge-plugins/homebridge-blink (or something like this).
Your GitHub repo would be transferred to the Homebridge Plugins organisation (you would have maintainer role, and the npm package would be under the Homebridge Plugins organization on npm.
The idea of this system is to try and reduce cases where there ends up being multiple plugins for the same brand.

This is totally up to you, just something to consider!

[BitWise-0x]

I can't find it. This is for unmaintained plugins so I assume it isn't it https://github.com/homebridge-plugins

[bwp91]

@BitWise-0x yes that's it! For a few months now, we have used it to store plugins all kinds of plugins, not just those which are unmaintained.

I meant to include this link in my message above, these are the currently scoped plugins we have + a bit more info about scoped plugins.

https://github.com/homebridge/plugins/wiki/Scoped-Plugins

[BitWise-0x]

Would I retain full autonomy over releases and the npm publish pipeline, or would there be review/approval from the org?

[bwp91]

@BitWise-0x there isn't any review or approval at all. you can decide yourself which things you work on, how often you want to release, etc. We also wouldn't allow any write/maintain role to anyone else, unless

• you specifically ask us to
• it seems like you go missing (e.g. at least 6 months have gone since your last ticket reply/commit)

For npm publishing, i would need to add a new workflow to the repo on GitHub, like this. You can edit this file if you wanted to, like if you added a step for some unit testing.

[BitWise-0x]

sorry about the back and forth, I guess I don't see the benefit. Ranking? Do you need this for verification? I'd like to think about it...