Summary
Togoder Security scanned the npm package js-yaml@4.1.0 on May 15, 2026. An AI review of 26 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 |
|---|---|---|
| binary.js | safe | No malicious patterns detected; the code is a legitimate implementation for YAML binary data resolution, construction, and representation using standard base64 encoding logic. |
| bool.js | safe | No malicious patterns detected |
| common.js | safe | No malicious patterns detected |
| core.js | safe | The code is a standard module re-export from a legitimate YAML parsing library with no malicious patterns detected. |
| default.js | safe | No malicious patterns detected |
| dumper.js | safe | The code is a standard YAML serialization utility that safely processes and formats JavaScript objects into YAML strings without any network calls, process spawning, or obfuscation. |
| exception.js | safe | No malicious patterns detected |
| failsafe.js | safe | No malicious patterns detected |
| float.js | safe | No malicious patterns detected |
| index.js | safe | No malicious patterns detected |
| int.js | safe | No malicious patterns detected |
| js-yaml.js | safe | No malicious patterns detected |
| json.js | safe | No malicious patterns detected |
| loader.js | safe | No malicious patterns detected |
| map.js | safe | No malicious patterns detected |
| merge.js | safe | No malicious patterns detected |
| null.js | safe | No malicious patterns detected |
| omap.js | safe | No malicious patterns detected |
| pairs.js | safe | No malicious patterns detected |
| schema.js | safe | No malicious patterns detected |
| seq.js | safe | No malicious patterns detected |
| set.js | safe | No malicious patterns detected |
| snippet.js | safe | The code is a legitimate snippet generation utility for displaying source code context around a position, with no security concerns detected. |
| str.js | safe | The code is a standard, benign YAML scalar type definition with no suspicious or malicious patterns detected. |
| timestamp.js | safe | No malicious patterns detected |
Show 1 more file
| File | Verdict | What the reviewer saw |
|---|---|---|
| type.js | safe | No malicious patterns detected |
Affected version ranges
None of the 2 scanned versions of js-yaml are flagged high or critical. The latest scanned version, 4.3.2, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 4.3.2 | No issues | 1 | 4.3.2 | |
| 4.1.1 – 4.3.0 | Not scanned | 2 | >=4.1.1 <=4.3.0 | |
| 4.1.0 | No issues | 1 | 4.1.0 | |
| 3.15.0 – 3.15.2 | Not scanned | 2 | >=3.15.0 <=3.15.2 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of js-yaml
Frequently asked questions
Is js-yaml safe to use?
Our AI source review of js-yaml@4.1.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does js-yaml contain malware?
No malware was identified in js-yaml@4.1.0 when Togoder Security scanned it on May 15, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was js-yaml checked?
Togoder Security downloaded the published npm package and had an AI model read its 26 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 js-yaml 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 js-yaml@4.1.0, cost nothing.