Skip to content
Nautilus SecureSDLC

[Nautilus SecureSDLC] Ref:main Event:push #2

Sign in to view logs

[Nautilus SecureSDLC] Ref:main Event:push

[Nautilus SecureSDLC] Ref:main Event:push #2

Triggered via push July 28, 2025 18:27
@CruzMolinaCruzMolina
pushed 980545e
main
Status Success
Total duration 3m 26s
Artifacts 1

securesdlc.yml

on: push
securesdlc-umbrella  /  ...  /  Repo visibility check
4s
securesdlc-umbrella / securesdlc-sast / Repo visibility check
securesdlc-umbrella  /  ...  /  Repo visibility check
3s
securesdlc-umbrella / securesdlc-sca / Repo visibility check
securesdlc-umbrella  /  ...  /  SecureSDLC Zizmor
22s
securesdlc-umbrella / securesdlc-zizmor / SecureSDLC Zizmor
securesdlc-umbrella  /  ...  /  SecureSDLC SAST
2m 1s
securesdlc-umbrella / securesdlc-sast / SecureSDLC SAST
securesdlc-umbrella  /  ...  /  SecureSDLC SCA
3m 14s
securesdlc-umbrella / securesdlc-sca / SecureSDLC SCA
Fit to window
Zoom out
Zoom in

Annotations

1 warning
securesdlc-umbrella / securesdlc-zizmor / SecureSDLC Zizmor
No file matched to [**/*(requirements|constraints)*.(txt|in),**/pyproject.toml,**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.

Artifacts

Produced during runtime
Name Size Digest
Zizmor scan results Expired
3.22 KB
sha256:1f590085b489676c10293d69fdfd73aa66b0e93a83fd6ef0b18688482b5c131a