jsx-eslint/eslint-plugin-react

no-danger does not report dangerouslySetInnerHTML usage in React.createElement

Open

#4,004 opened on May 4, 2026

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)JavaScript (2,734 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (9,293 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

The no-danger rules only reports dangerouslySetInnerHTML when it's used in JSX, but not when it's used in React.createElement

To be fair, it's mentioned in the rule description, but it took me a bit to see this. Also, the similar no-danger-with-children rule does report usage in React.createElement, so it would be nice to be consistent here.

Contributor guide

Research direction
Examine the source of the `no danger` rule and compare it with `no danger with children` to understand why `React.createElement` is not caught. Then implement the missing check.
Tech stack
javascriptreact
Domain
frontenddeveloper experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptReactESLintGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65