Skip to content
Security Scan

Security Scan #106

Sign in to view logs

Security Scan

Security Scan #106

Triggered via schedule May 11, 2026 05:55
@JosephrpJosephrp
⁠ 280f272
main
Status Failure
Total duration 23s
Artifacts –

security-scan.yml

on: schedule
Secrets Detection
4s
Secrets Detection
Python Dependency Scan
10s
Python Dependency Scan
Node.js Dependency Scan
5s
Node.js Dependency Scan
Python SAST (Bandit)
3s
Python SAST (Bandit)
Python SAST (Semgrep)
4s
Python SAST (Semgrep)
Python Security Linting (Ruff)
3s
Python Security Linting (Ruff)
Frontend SAST (ESLint Security)
4s
Frontend SAST (ESLint Security)
DAST (OWASP ZAP)
4s
DAST (OWASP ZAP)
Generate Security Report
9s
Generate Security Report
Security Gate
2s
Security Gate
Fit to window
Zoom out
Zoom in

Annotations

10 errors
Python Security Linting (Ruff)
The job was not started because your account is locked due to a billing issue.
Python SAST (Bandit)
The job was not started because your account is locked due to a billing issue.
Python SAST (Semgrep)
The job was not started because your account is locked due to a billing issue.
Secrets Detection
The job was not started because your account is locked due to a billing issue.
DAST (OWASP ZAP)
The job was not started because your account is locked due to a billing issue.
Frontend SAST (ESLint Security)
The job was not started because your account is locked due to a billing issue.
Node.js Dependency Scan
The job was not started because your account is locked due to a billing issue.
Python Dependency Scan
The job was not started because your account is locked due to a billing issue.
Generate Security Report
The job was not started because your account is locked due to a billing issue.
Security Gate
The job was not started because your account is locked due to a billing issue.
⚡