react-syntax-highlighter
syntax highlighting component for react with prismjs or highlightjs ast using inline styles
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate maintainer transition from conorhastings to simmerer within the react-syntax-highlighter GitHub org; simmerer has a strong track record (49 approved, 0 rejected). | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): highlightjs-vue is a legitimate highlight.js language extension consistent with this package's purpose; addition is benign and expected for Vue syntax support. | ai | |
| source-diff | large-new-source-files | AI (source-diff): react-syntax-highlighter routinely ships large numbers of generated language/theme definition files for highlight.js and prismjs; this is expected build output, not injected code. | ai | |
| dependencies | unvetted-dep:prismjs | AI (dependencies): prismjs is a core, well-known syntax highlighting library and a fundamental dependency of react-syntax-highlighter by design. Stable false positive for this package. | ai |
Versions (showing 51 of 119)
| Version | Deps | Published |
|---|---|---|
| 16.1.1 | 6 / 38 | |
| 16.1.0 | 6 / 37 | |
| 16.0.0 | 6 / 36 | |
| 15.6.6 | 6 / 36 | |
| 15.6.5 | 6 / 36 | |
| 15.6.4 | 6 / 36 | |
| 15.6.2 | 6 / 36 | |
| 15.6.1 | 6 / 36 | |
| 15.5.0 | 5 / 36 | |
| 15.4.1 | 5 / 36 | |
| 15.4.0 | 5 / 36 | |
| 15.3.0 | 5 / 36 | |
| 15.2.0 | 5 / 36 | |
| 15.1.0 | 5 / 36 | |
| 15.0.0 | 5 / 36 | |
| 14.0.2 | 5 / 36 | |
| 14.0.0 | 5 / 36 | |
| 13.5.3 | 5 / 36 | |
| 13.5.2 | 5 / 36 | |
| 13.5.1 | 5 / 36 | |
| 13.5.0 | 5 / 36 | |
| 13.4.0 | 5 / 35 | |
| 13.3.1 | 5 / 30 | |
| 13.2.1 | 5 / 30 | |
| 13.2.0 | 5 / 30 | |
| 13.1.0 | 5 / 30 | |
| 13.0.0 | 5 / 30 | |
| 12.2.1 | 5 / 30 | |
| 12.1.0 | 5 / 30 | |
| 12.0.2 | 5 / 30 | |
| 12.0.1 | 5 / 30 | |
| 12.0.0 | 5 / 30 | |
| 11.0.3 | 5 / 30 | |
| 11.0.2 | 5 / 30 | |
| 11.0.1 | 5 / 30 | |
| 11.0.0 | 5 / 30 | |
| 10.3.5 | 5 / 30 | |
| 10.3.4 | 5 / 30 | |
| 10.3.3 | 5 / 30 | |
| 10.3.2 | 5 / 30 | |
| 10.3.1 | 5 / 30 | |
| 10.3.0 | 5 / 30 | |
| 10.2.1 | 5 / 30 | |
| 10.2.0 | 5 / 30 | |
| 10.1.3 | 5 / 30 | |
| 10.1.2 | 5 / 29 | |
| 10.1.1 | 5 / 30 | |
| 10.1.0 | 5 / 27 | |
| 10.0.1 | 5 / 27 | |
| 10.0.0 | 5 / 27 | |
| 9.0.1 | 5 / 22 |
v16.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.0
2 findingsThis version was published by a different npm account than previous versions on 2022-03-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.