Summary
Togoder Security scanned the npm package lz-string@1.5.0 on Oct 6, 2026. An AI review of 4 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| bin/bin.js | safe | No malicious patterns detected |
| libs/base64-string.js | safe | No malicious patterns detected; code is a legitimate LZ-String compression library with no network, filesystem, environment, or execution risks. |
| libs/lz-string.js | safe | The code is a legitimate LZ-string compression algorithm implementation with no malicious patterns, network activity, or shell execution. |
| reference/lz-string-1.0.2.js | safe | Cleared by Jev triage; no further analysis needed |
Frequently asked questions
Is lz-string safe to use?
Our AI source review of lz-string@1.5.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does lz-string contain malware?
No malware was identified in lz-string@1.5.0 when Togoder Security scanned it on Oct 6, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was lz-string checked?
Togoder Security downloaded the published npm package and had an AI model read its 4 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan lz-string together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in lz-string@1.5.0, cost nothing.