Summary
Togoder Security scanned the npm package libnpmpublish@11.2.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 |
|---|---|---|
| lib/index.js | safe | The entry point simply re-exports two local modules with no obfuscation, network activity, or execution of untrusted code. |
| lib/provenance.js | safe | No malicious patterns detected |
| lib/publish.js | safe | No malicious patterns detected; the code is a legitimate npm publish module that handles provenance signing and does not exfiltrate data, execute dynamic code, or perform suspicious operations. |
| lib/unpublish.js | safe | No malicious patterns detected |
Frequently asked questions
Is libnpmpublish safe to use?
Our AI source review of libnpmpublish@11.2.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does libnpmpublish contain malware?
No malware was identified in libnpmpublish@11.2.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 libnpmpublish 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 libnpmpublish 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 libnpmpublish@11.2.0, cost nothing.