RepoPilot

tsenart/vegeta · Security & risks

Authoritative risk signals for tsenart/vegeta — dependency CVEs (deps.dev), OpenSSF Scorecard, and GitHub Code Scanning. Not a substitute for your own security review.

ArchitectureSecurity & risksDependenciesLicenseMaintenanceAlternativesVsFull analysis

Dependency CVEs (deps.dev)

0
Critical
0 direct
0
High
0 direct
1
Moderate
49
Deps scanned
16 direct
  • GO-2026-5932 · golang.org/x/cryptoThe golang.org/x/crypto/openpgp package is unmaintained, unsafe by design, and has known security issuesMODERATE

OpenSSF Scorecard · 3.6/10

  • Packaging—
  • Branch-Protection—
  • Code-Review0/10
  • Maintained0/10
  • Token-Permissions0/10
  • CII-Best-Practices0/10
  • Security-Policy0/10
  • Fuzzing0/10

Ask AI about tsenart/vegeta

Grounded in the actual source code. Pick a starter question or write your own.

What does this repo do, in one paragraph?How would I get started using it?What are the main alternatives?Show me the entry point.
Or write your own question

Informational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.