Verification Request: @sealad886/homebridge-blink-cameras-new-api

[sealad886]

Plugin Name

@sealad886/homebridge-blink-cameras-new-api

Link To GitHub Repo

https://github.com/sealad886/homebridge-blink-cameras-new-api

Plugin Icon (Optional)

none in use currently

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

I was the first to publish a functioning plugin after Amazon/Blink suddenly changed their API endpoints late last year. While I learned a lot from existing plugins (and the many of them that implemented various Blink login functionalities), this plugin is truly novel in that it fully utilizes the new API endpoints and automates discovery for the user as much as is possible. I plan to continue to develop it, as it's something I personally use and would like to see new features in.

[github-actions]

🔴 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.
• Dependencies: homebridge was installed as a dependency
• Dependencies: hap-nodejs was installed as a dependency

🟢 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 (v0.7.0-alpha.2) matches NPM version (v0.7.0-alpha.2)
• 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
• 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 scripts/preuninstall.js

ℹ️ Check Details

• These checks were run against v0.7.0-alpha.2 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.

[sealad886]

Hi — the three issues identified in the automated check have been addressed in v0.7.0 (just published to npm):

1. Config Schema JSON (required field misuse): The schema was already corrected prior to the bot's check running against the published version. required is now an array at the object level ("required": ["name"]), not a boolean on individual properties.

2. homebridge installed as a dependency: Removed the peerDependencies block for homebridge. The version requirement is declared via engines.homebridge (which the verification check validates separately). The peerDependencies entry was causing npm 7+ to auto-install homebridge into node_modules, which triggered the filesystem check failure.

3. hap-nodejs installed as a dependency: Resolved as a side-effect of fix Review request for homebridge-chamberlain #2 — hap-nodejs was a transitive dependency of the auto-installed homebridge peer dep.

I've verified locally by simulating the bot's check: clean npm install of the packed tarball in an empty directory confirms neither homebridge nor hap-nodejs appear in node_modules.

/check

[sealad886]

/check

[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.4
• Package JSON: initializer function found
• NPM Package: has not been deprecated
• GitHub Repo: version in package.json (v0.7.0) matches NPM version (v0.7.0)
• 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
• 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 scripts/preuninstall.js

ℹ️ Check Details

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

📋 Next Steps

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

[bwp91]

Hi @sealad886

We currently have these plugins marked as verified

• https://www.npmjs.com/package/homebridge-blink-for-home-new
• https://www.npmjs.com/package/@jackietreeh0rn/homebridge-blink-security

Does your plugin differ functionality-wise from either of these?

Thanks!