tldjs
1
Versions
—
License
Yes
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
thom4
Keywords
tldslddomainbrowseruriurldomain namesubdomainpublic suffix
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): tldjs postinstall fetches the Public Suffix List from publicsuffix.org — documented and necessary for the library's core function. Stable pattern across all versions. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP 192.168.0.1 appears in benchmark.js as a test URL for parsing edge cases, not a network request to a suspicious host. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): require(pathJoin(__dirname, '..', 'lib', 'updater')) is a fixed relative path to a local module, not arbitrary dynamic loading. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.3.2 | 1 / 11 |
v2.3.2
2 findings
HIGH
Package has 'postinstall' script
install-scripts
Script: node ./bin/postinstall.js
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.