Summary
Togoder Security scanned the npm package sigstore@4.1.1 on Oct 6, 2026. An AI review of 3 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 |
|---|---|---|
| dist/config.js | safe | No malicious patterns detected; the code is a legitimate Sigstore configuration module with no data exfiltration, credential harvesting, obfuscation, or suspicious execution. |
| dist/index.js | safe | No malicious patterns detected; the file is a standard re-export module for the Sigstore JavaScript library. |
| dist/sigstore.js | safe | No malicious patterns detected; the code is a legitimate Sigstore signing/verification library using standard Node.js modules and TUF for trust root retrieval. |
Scanned versions of sigstore
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 4.1.1 | No issues | 3 | Oct 6, 2026 |
Frequently asked questions
Is sigstore safe to use?
Our AI source review of sigstore@4.1.1 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does sigstore contain malware?
No malware was identified in sigstore@4.1.1 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 sigstore checked?
Togoder Security downloaded the published npm package and had an AI model read its 3 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 sigstore 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 sigstore@4.1.1, cost nothing.