# @sigstore/core@3.2.1 security report (npm)

- Verdict: **No issues** (risk level: safe)
- Scanned: 2026-10-06T14:23:02.000Z
- Files reviewed: 22
- Findings: no findings
- Report: https://security.togoder.click/npm/@sigstore/core
- Source: Togoder Security (https://security.togoder.click), AI source-code review

## Summary

Togoder Security scanned the npm package @sigstore/core@3.2.1 on Oct 6, 2026. An AI review of 22 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.

## Findings

No findings.

## Files reviewed

- `dist/asn1/error.js` (safe): No malicious patterns detected; the file only defines two custom error classes with no side effects.
- `dist/asn1/index.js` (safe): This is a simple, legitimate module that re-exports ASN1Obj from './obj' with no malicious patterns.
- `dist/asn1/length.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/asn1/obj.js` (safe): No malicious patterns detected; this is a legitimate ASN.1 DER parsing module from the Sigstore project with no network, filesystem, process, or dynamic code execution behavior.
- `dist/asn1/parse.js` (safe): No malicious patterns detected
- `dist/asn1/tag.js` (safe): No malicious patterns detected; the code is a legitimate ASN.1 tag parser from the Sigstore project with no network, filesystem, process execution, or obfuscation concerns.
- `dist/crypto.js` (safe): No malicious patterns detected; the code is a legitimate cryptographic utility from the Sigstore project using Node.js crypto for public key creation, hashing, verification, and timing-safe comparison.
- `dist/dsse.js` (safe): No malicious patterns detected; the code implements standard DSSE pre-authentication encoding for Sigstore without any network, filesystem, or process manipulation.
- `dist/encoding.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/index.js` (safe): The file is a standard TypeScript/CommonJS re-export module for the Sigstore JS library with no malicious patterns detected.
- `dist/json.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/oid.js` (safe): The file only exports static OID-to-hash-algorithm mappings and contains no malicious or suspicious patterns.
- `dist/pem.js` (safe): No malicious patterns detected
- `dist/rfc3161/error.js` (safe): No malicious patterns detected
- `dist/rfc3161/index.js` (safe): No malicious patterns detected
- `dist/rfc3161/timestamp.js` (safe): Code is a benign RFC3161 timestamp parser/verifier from Sigstore with no malicious patterns detected
- `dist/rfc3161/tstinfo.js` (safe): No malicious patterns detected; the file implements RFC 3161 timestamp parsing and verification using only local cryptographic operations without network, filesystem, or process execution.
- `dist/stream.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/x509/cert.js` (safe): No malicious patterns detected; the code is a standard X.509 certificate parser from the Sigstore project.
- `dist/x509/ext.js` (safe): No malicious patterns detected; the file contains only X.509 certificate extension parsing logic with no network, filesystem, process execution, or obfuscation concerns.
- `dist/x509/index.js` (safe): No malicious patterns detected
- `dist/x509/sct.js` (safe): No malicious patterns detected

AI analysis is guidance, not a guarantee. Methodology: https://security.togoder.click/methodology
