@sigstore/verify
Verification of Sigstore signatures
84%
Total Score
healthy
Healthy, with active releases and organization-backed maintenance outweighing minor workflow and package-link concerns.
Health Score Breakdown
The repository name does not match the package and its README does not mention @sigstore/verify, so the package-to-repository relationship is less transparent despite the organization-backed monorepo context.
All nine workflows were analyzed, use read-only permissions, and pin all 32 action references. Two high-confidence bot-condition findings and two low-severity adhoc-package findings are real hygiene concerns, but no untrusted checkout or script-injection paths were found.
Vulnerabilities
| Title | Versions | Severity |
|---|---|---|
CVE-2026-48816 @sigstore/verify is vulnerable to Insufficient Verification of Data Authenticity in versions 3.1.0 - 3.1.0. | 3.1.0 - 3.1.0 | Medium |
Package versions
Maintainers
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 @sigstore/core Version ^4.0.1 | — | — |
@sigstore/bundle Version ^5.0.0 | — | — |
@sigstore/protobuf-specs Version ^0.5.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 months ago
- Created
- 2 years ago
- Unpacked Size
- 0.1 MB
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.