Skip to content
This repository has been archived by the owner on Dec 23, 2024. It is now read-only.
Microsoft Defender For Devops

[StepSecurity] Apply security best practices #3

Sign in to view logs

[StepSecurity] Apply security best practices

[StepSecurity] Apply security best practices #3

Triggered via pull request May 4, 2024 19:10
@step-security-botstep-security-bot
opened #2
step-security-bot:stepsecurity_remediation_1714849798
Status Success
Total duration 2m 16s
Artifacts –

defender-for-devops.yml

on: pull_request
MSDO
2m 4s
MSDO
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
MSDO
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-dotnet@3447fd6a9f9e57506b15f895c5b76d3b197dc7c2, microsoft/security-devops-action@e94440350ed10e2806d47cd0d7504a2c51abdbe9, github/codeql-action/upload-sarif@ceaec5c11a131e0d282ff3b6f095917d234caace. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
MSDO
CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/
MSDO
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration