html-to-image

npm

Is html-to-image safe to use?

The latest brin safety scan flagged html-to-image v1.11.13 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 65/100. Review the findings below before use. This is an automated assessment and may contain errors.

Install (safety-checked)

html-to-image Has Warnings

Warnings detected due to potential concerns

warning
CVEs

0

Threats

0

Install Scripts

0

Risk Indicators

  • Can spawn child processes

brin Recommendations

  • This package has warnings detected. Evaluate the specific concerns before proceeding.

Install with brin add html-to-image to automatically apply these checks before installation.

This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.

html-to-image Capabilities & Permissions

What html-to-image can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Network Access

This package makes network requests.

developer.mozilla.orgstackoverflow.comwww.w3.org
Protocols: http, https

Process Spawning

This package can spawn child processes.

AGENTS.md for html-to-image

Good instructions lead to good results. brin adds html-to-image documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.

brin init

Vercel's research: 100% accuracy with AGENTS.md vs 53% without →

html-to-image Documentation & Source Code

For the full html-to-image README, API documentation, and source code, visit the official package registry.

Frequently asked questions about html-to-image safety

Weekly Downloads

1.7M

Version

1.11.13

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: developer.mozilla.org, stackoverflow.com, www.w3.org

Process

Spawns child processes

Is html-to-image Safe? | npm Safety Scan - brin