Skip to content
Security Scan

Security Scan #103

Sign in to view logs

Security Scan

Security Scan #103

Triggered via schedule April 20, 2026 04:55
@JosephrpJosephrp
⁠ 280f272
main
Status Failure
Total duration 10s
Artifacts –

security-scan.yml

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

Annotations

10 errors
DAST (OWASP ZAP)
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.
Python SAST (Semgrep)
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 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 Dependency Scan
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.
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.
⚡