Skip to content
Security Scan

Security Scan #453

Sign in to view logs

Security Scan

Security Scan #453

Triggered via schedule March 9, 2026 13:28
@alexandearalexandear
⁠ fef9f98
main
Status Failure
Total duration 43s
Artifacts –

security.yml

on: schedule
Scan for vulnerabilities in Go code
39s
Scan for vulnerabilities in Go code
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
Scan for vulnerabilities in Go code
internal.App.doCommitsForProject calls git.Worktree.Commit, which eventually calls fp25519.Inv
Scan for vulnerabilities in Go code
internal.App.doCommitsForProject calls git.Worktree.Commit, which eventually calls fp25519.Cswap
Scan for vulnerabilities in Go code
internal.App.doCommitsForProject calls git.Worktree.Commit, which eventually calls fp25519.Cmov
Scan for vulnerabilities in Go code
internal.App.doCommitsForProject calls git.Worktree.Commit, which eventually calls fp25519.Add
Scan for vulnerabilities in Go code
internal.init calls object.init, which eventually calls ed448.init
Scan for vulnerabilities in Go code
internal.App.doCommitsForProject calls git.Worktree.Commit, which eventually calls ed448.Sign
Scan for vulnerabilities in Go code
internal.init calls object.init, which eventually calls ed25519.init
Scan for vulnerabilities in Go code
internal.App.doCommitsForProject calls git.Worktree.Commit, which eventually calls ed25519.Sign
Scan for vulnerabilities in Go code
internal.init calls object.init, which eventually calls conv.init
Scan for vulnerabilities in Go code
internal.App.doCommitsForProject calls git.Worktree.Commit, which eventually calls conv.BytesLe2BigInt
Scan for vulnerabilities in Go code
Failed to restore: Cache service responded with 400