← Home

highlight-words-core

npm Repository

Utility functions shared by react-highlight-words and react-native-highlight-words

11
Versions
MIT
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

ryanflorencebrianvaughnclauderic

Keywords

highlighterhighlighttextwordsmatchessubstringoccurrencessearch

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from clauderic to brianvaughn occurred in 2017; brianvaughn is the listed author and GitHub repo owner. Legitimate transition. ai
phantom-deps phantom-dep:babel-runtime AI (phantom-deps): babel-runtime is injected by babel-plugin-transform-runtime at build time; not directly imported but correctly declared as a runtime dependency. ai

Versions (showing 11 of 11)

Version Deps Published
1.2.3 0 / 13
1.2.2 0 / 13
1.2.1 1 / 12
1.2.0 0 / 12
1.1.2 0 / 12
1.1.1 1 / 18
1.1.0 1 / 18
1.0.3 1 / 18
1.0.2 1 / 18
1.0.1 1 / 17
1.0.0 1 / 17

v1.2.3

1 finding
LOW No provenance attestation provenance

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

v1.2.2

1 finding
LOW No provenance attestation provenance

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

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

2 findings
HIGH Publisher changed: clauderic → brianvaughn (on 2017-10-15) provenance

This version was published by a different npm account than previous versions on 2017-10-15. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: brianvaughn → clauderic (on 2016-09-22) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-09-22. This could indicate a legitimate maintainer transition or an account compromise.

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.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.