tilt-dev/tilt · Security & risks
Authoritative risk signals for tilt-dev/tilt — 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
0
Moderate
16
Deps scanned
2 direct
OpenSSF Scorecard · 4.5/10
- Token-Permissions—
- Packaging—
- Dangerous-Workflow—
- Branch-Protection—
- CII-Best-Practices0/10
- Fuzzing0/10
- Signed-Releases0/10
- SAST0/10
Ask AI about tilt-dev/tilt
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.