@teambit/react.ui.component-highlighter
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
teambit-ownershohamgiladdavidfirstranm8guysaaritaymendelerezbitjoshk2redigmayona007
Keywords
bitcomponentscollaborationwebreactreact-components
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Scoped component package from teambit; missing description is a consistent pattern across their component library, not a malware signal. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes 150+ versions of this package without provenance; consistent pattern for this publisher. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known polyfill runtime dep; phantom-dep false positive for this package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.2.5 | 15 / 11 |
v0.2.5
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.