Summary
Togoder Security scanned the npm package text-encoding-utf-8@1.0.2 on Oct 4, 2026. An AI review of 5 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 |
|---|---|---|
| lib/encoding.js | safe | No malicious patterns detected; the code is a standard TextEncoder/TextDecoder polyfill with no network, filesystem, process, or dynamic execution behavior. |
| lib/encoding.lib.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/encoding.lib.mjs | safe | Cleared by Jev triage; no further analysis needed |
| src/encoding.js | safe | Cleared by Jev triage; no further analysis needed |
| src/polyfill.js | safe | No malicious patterns detected; the code only polyfills TextDecoder and TextEncoder globals with no network, filesystem, or process access. |
Scanned versions of text-encoding-utf-8
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 1.0.2 | No issues | 5 | Oct 4, 2026 |
Frequently asked questions
Is text-encoding-utf-8 safe to use?
Our AI source review of text-encoding-utf-8@1.0.2 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does text-encoding-utf-8 contain malware?
No malware was identified in text-encoding-utf-8@1.0.2 when Togoder Security scanned it on Oct 4, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was text-encoding-utf-8 checked?
Togoder Security downloaded the published npm package and had an AI model read its 5 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 text-encoding-utf-8 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 text-encoding-utf-8@1.0.2, cost nothing.