Summary
Togoder Security scanned the npm package @sigstore/bundle@4.0.0 on Oct 6, 2026. An AI review of 7 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/build.js | safe | No malicious patterns detected; the code is a legitimate Sigstore bundle builder with no network, filesystem, process, or obfuscated operations. |
| dist/bundle.js | safe | No malicious patterns detected |
| dist/error.js | safe | No malicious patterns detected |
| dist/index.js | safe | This is a standard Sigstore bundle library index file with only re-exports and no malicious patterns detected. |
| dist/serialized.js | safe | No malicious patterns detected; the code is a straightforward Sigstore bundle serialization utility using protobuf-specs. |
| dist/utility.js | safe | No malicious patterns detected |
| dist/validate.js | safe | The code performs only local validation of Sigstore bundle structure with no network, filesystem, process, or dynamic execution behavior. |
Scanned versions of @sigstore/bundle
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 4.0.0 | No issues | 7 | Oct 6, 2026 |
Frequently asked questions
Is @sigstore/bundle safe to use?
Our AI source review of @sigstore/bundle@4.0.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @sigstore/bundle contain malware?
No malware was identified in @sigstore/bundle@4.0.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 @sigstore/bundle checked?
Togoder Security downloaded the published npm package and had an AI model read its 7 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/bundle 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/bundle@4.0.0, cost nothing.