← Home

linkifyjs

npm Repository Homepage

Find URLs, email addresses, #hashtags and @mentions in plain-text strings, then convert them into HTML <a> links.

18
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

nfrasser

Keywords

autolinkemailhashtaghtmljquerylinkmentionreacttwitterurl

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Migrated to GitHub Actions CI/CD publishing with SLSA provenance; same repo owner. ai
publish-pattern dormant-publish AI (publish-pattern): Mature stable package; infrequent releases are normal, CI/CD provenance confirms legitimacy. ai
source-diff obfuscated-file:dist/linkify.cjs AI (source-diff): Standard bundled/minified dist output with encoded IANA TLD data; expected for this package's build process. ai
source-diff obfuscated-file:dist/linkify.mjs AI (source-diff): Standard bundled/minified dist output with encoded IANA TLD data; expected for this package's build process. ai

Versions (showing 18 of 18)

Version Deps Published
4.3.3 0 / 0
4.3.2 0 / 0
2.1.9 0 / 41
2.1.8 3 / 38
2.1.7 3 / 38
2.1.6 3 / 39
2.1.5 3 / 37
2.1.4 3 / 37
2.1.3 3 / 38
2.1.2 3 / 38
2.1.1 3 / 38
2.1.0 3 / 38
2.0.5 1 / 39
2.0.4 1 / 39
2.0.3 1 / 39
2.0.2 1 / 39
2.0.1 1 / 39
2.0.0 1 / 35

v4.3.3

2 findings
HIGH Publisher changed: nfrasser → GitHub Actions (on 2026-05-13) provenance

This version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.3.2

1 finding
LOW No provenance attestation provenance

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