← Home

htmltojsx

npm Repository Homepage

Converts HTML to JSX for use with React

8
Versions
BSD-3-Clause
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

daniel15fb

Keywords

reactjsxhtmltojsxhtmlreact-component

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): child_process usage is in gulpfile.js (build tooling only), not in runtime code. Standard pattern for gulp-based build systems; not a runtime risk. ai
bogus-package bogus-package AI (bogus-package): The 'fb' spam flag refers to the Facebook/Meta npm account, a known legitimate publisher in the React ecosystem. False positive for this package. ai
phantom-deps phantom-dep:react AI (phantom-deps): React is a legitimate runtime dependency for this JSX converter; phantom detection is a false positive due to indirect/JSX usage patterns. ai

Versions (showing 8 of 8)

Version Deps Published
0.3.0 4 / 12
0.2.6 3 / 12
0.2.5 3 / 9
0.2.4 3 / 9
0.2.3 3 / 9
0.2.2 2 / 9
0.2.1 2 / 9
0.2.0 2 / 8

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.