k3d-io/k3d · Security & risks
Authoritative risk signals for k3d-io/k3d — dependency CVEs (deps.dev), OpenSSF Scorecard, and GitHub Code Scanning. Not a substitute for your own security review.
Dependency CVEs (deps.dev)
0
Critical
0 direct
0
High
0 direct
2
Moderate
59
Deps scanned
9 direct
- GO-2022-0635 · github.com/aws/aws-sdk-goIn-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-goMODERATE
- GO-2022-0646 · github.com/aws/aws-sdk-goCBC padding oracle issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-goMODERATE
OpenSSF Scorecard · 4.2/10
- Packaging—
- Branch-Protection—
- Token-Permissions0/10
- CII-Best-Practices0/10
- Fuzzing0/10
- Signed-Releases0/10
- Security-Policy0/10
- Pinned-Dependencies0/10
Ask AI about k3d-io/k3d
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 questionInformational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.