Skip to content
Security Scanning

fix: use correct boto3 service name for evaluation client (#267) #4

Sign in to view logs

fix: use correct boto3 service name for evaluation client (#267)

fix: use correct boto3 service name for evaluation client (#267) #4

Triggered via push February 16, 2026 15:11
@afarntrogafarntrog
pushed 1e2be1b
main
Status Success
Total duration 14s
Artifacts 1

security-scanning.yml

on: push
Secret Scanning
9s
Secret Scanning
Bandit Security Scan
11s
Bandit Security Scan
Safety Dependency Check
11s
Safety Dependency Check
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Safety Dependency Check
No files were found with the provided path: safety-report.json. No artifacts will be uploaded.

Artifacts

Produced during runtime
Name Size Digest
bandit-results Expired
1.18 KB
sha256:d23b9d86a786fd90c23c831a5b723112fb4779a1ca8da343968344b074d78102