Summary
Togoder Security scanned the npm package gopd@1.2.0 on Oct 4, 2026. An AI review of 2 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 |
|---|---|---|
| gOPD.js | safe | Cleared by Jev triage; no further analysis needed |
| index.js | safe | No malicious patterns detected; this is a standard gOPD fallback wrapper with no network, filesystem, process, or dynamic code execution behavior. |
Scanned versions of gopd
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 1.2.0 | No issues | 2 | Oct 4, 2026 |
Frequently asked questions
Is gopd safe to use?
Our AI source review of gopd@1.2.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does gopd contain malware?
No malware was identified in gopd@1.2.0 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 gopd checked?
Togoder Security downloaded the published npm package and had an AI model read its 2 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 gopd 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 gopd@1.2.0, cost nothing.