New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add OSV scanner and GitHub actions to home page #2136
Add OSV scanner and GitHub actions to home page #2136
Conversation
<div id="use-the-github-action" class="mdc-layout-grid__cell--span-12 github-action"> | ||
<h2 class="heading">GitHub Action (OSV‑Scanner)</h2> | ||
<p class="description"> | ||
The <a href="https://github.com/google/osv-scanner-action" target="_blank">OSV-Scanner GitHub Action</a> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: we can make this a bit more concise.
OSV-Scanner also provides reusable GitHub workflows that can be easily integrated into CI/CD pipelines to provide continuous vulnerability scanning coverage. This can scan newly added dependencies in pull requests for introduced vulnerabilities, as well as perform regular vulnerability scans for the entire project.
</clipboard-copy> | ||
</div> | ||
<div class="code-card mdc-layout-grid__cell--span-6 mdc-layout-grid__cell--span-12-tablet"> | ||
<h3 class="code-card-title">Guided Remediation (advanced)</h3> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: replace advanced with interactive
Prior to this change the More details button on scanner CLT tool section, pointed to the osv-scanner github page. This change updates it to link to osv scanner documentation page instead.
This change adds a new section to Home page to display info about github action tool (OSV-Scanner).
Updated the PR. Here is how it looks like: Screen.Recording.2024-05-08.at.9.59.28.AM.mov |
@zahraaalizadeh thanks. Are your changes pushed? It looks like what's in this PR is not consistent with what's shown in your video. |
11986b4
to
3e92859
Compare
Oops! Just pushed it 😅 Thanks for the heads up! |
Thanks @zahraaalizadeh. I'm running this locally and I see this for GitHub actions: Which doesn't look like it's formatted correctly? |
</div> | ||
</div> | ||
<div id="use-the-github-action" class="mdc-layout-grid__cell--span-12 github-action"> | ||
<h2 class="heading">GitHub Action (OSV‑Scanner)</h2> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: we can just call this "GitHub Workflows"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated via 4d3076c
<a class="cta-primary link-button" href="#use-the-cli">CLI Tools</a> | ||
<a class="cta-primary link-button" href="#use-vulnerability-scanner">Vulnerability Scanner</a> | ||
<a class="cta-primary link-button" href="#use-remediation-tools">Remediation Tools</a> | ||
<a class="cta-primary link-button" href="#use-the-github-action">Github Action Tools</a> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Can we call this "GitHub Workflows"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
♻️ updated via 4d3076c
Thanks, @oliverchang. I couldn't reproduce the issue on my local machine. Could you let me know which browser and configuration you're using? This will help me further investigate the problem. |
I'm using Chrome 123.0.6312.134 on Chrome OS. |
My bad, please ignore. It looks like my local CSS was style somehow. It now renders correctly for me. |
This change adds:
osv-scanner fix
for both basic(non-interactive) and advanced (interactive) use cases.resolves #2085
Screen.Recording.2024-04-26.at.10.28.35.am.mov