GitHub
github.com › snyk › cli
GitHub - snyk/cli: Snyk CLI scans and monitors your projects for security vulnerabilities. · GitHub
Snyk CLI scans and monitors your projects for security vulnerabilities. - snyk/cli
Author snyk
34:32
Enhancing Code Security 🔒 : Integrate Snyk with GitHub Actions ...
Using Snyk Effectively with Github | Snyk
00:53
How to EASILY Check for Vulnerabilities with Snyk - YouTube
00:43
How to Analyze a Vulnerability from Snyk's Vulnerability Database ...
19:44
Find Vulnerabilities In Your Code With Snyk - YouTube
GitHub
github.com › snyk › actions
GitHub - snyk/actions: A set of GitHub actions for checking your projects for vulnerabilities. · GitHub
Starred by 644 users
Forked by 194 users
Languages HTML 58.8% | Shell 21.2% | Ruby 20.0%
GitHub
github.com › snyk › snyk-intellij-plugin
GitHub - snyk/snyk-intellij-plugin: Snyk Vulnerability Scanner for IDEs based on the IntelliJ platform · GitHub
Starred by 68 users
Forked by 36 users
Languages Kotlin 95.6% | HTML 3.5%
GitHub
github.com › Andrii-Grytsenko-OWASP › SnykVulnCheck
GitHub - Andrii-Grytsenko-OWASP/SnykVulnCheck: Snyk Vulnerability Checking tool · GitHub
SnykVulnCheck - Snyk Vulnerability Checking tool Tool for checking components from SBOM.json file (Software Bill of Material) against known vulnerabilities by using public API to Snyk Vulnerability DB (https://security.snyk.io/api) Tool is designed for running inside docker container or as an ordinary python script
Starred by 4 users
Forked by 2 users
Languages Python 97.2% | Dockerfile 1.5% | Batchfile 1.3%
Snyk
docs.snyk.io › scan-fix-and-prevent › scan-with-snyk › snyk-open-source › manage-vulnerabilities › snyk-vulnerability-database
Snyk Vulnerability Database | Scan, fix, and prevent | Snyk User Docs
2 weeks ago - Monitoring user activity on GitHub, including issues, PRs, and commit messages that may indicate a vulnerability. Bulk research, using tools that look for repeated security mistakes across open-source package code.
GitHub
github.com › JLLeitschuh › snyk
GitHub - JLLeitschuh/snyk: CLI and build-time tool to find & fix known vulnerabilities in open-source dependencies · GitHub
CLI and build-time tool to find & fix known vulnerabilities in open-source dependencies - JLLeitschuh/snyk
Author JLLeitschuh
GitHub
github.com › snyk › vulncost
GitHub - snyk/vulncost: Find security vulnerabilities in open source npm packages while you code
Starred by 211 users
Forked by 37 users
Languages JavaScript 100.0% | JavaScript 100.0%
GitHub
github.com › cybersecurity-team › snyk
GitHub - cybersecurity-team/snyk: CLI and build-time tool to find & fix known vulnerabilities in open-source dependencies · GitHub
CLI and build-time tool to find & fix known vulnerabilities in open-source dependencies - cybersecurity-team/snyk
Author cybersecurity-team
GitHub
github.com › snyk-labs › nodejs-goof
GitHub - snyk-labs/nodejs-goof: Super vulnerable todo list application · GitHub
Super vulnerable todo list application. Contribute to snyk-labs/nodejs-goof development by creating an account on GitHub.
Starred by 548 users
Forked by 3.5K users
Languages JavaScript 53.3% | CSS 17.7% | Shell 14.7% | EJS 8.9% | Handlebars 4.6% | Dockerfile 0.6% | HTML 0.2%
GitHub
github.com › lirantal › vulndb
GitHub - lirantal/vulndb: Snyk's public vulnerability database
This is the vulnerability database used by Snyk, a tool that helps you find and fix known vulnerabilities in your Node.js dependencies, both ad hoc and as part of your CI (Build) system.
Author lirantal
GitHub
github.com › TomFoyster › snyk
GitHub - TomFoyster/snyk: CLI and build-time tool to find & fix known vulnerabilities in npm dependencies · GitHub
Snyk helps you find, fix and monitor for known vulnerabilities in Node.js npm, Ruby and Java dependencies, both on an ad hoc basis and as part of your CI (Build) system.
Author TomFoyster
Snyk
labs.snyk.io › resources › exploring-vulnerabilities-github-actions
Call for action: Exploring vulnerabilities in Github Actions | Snyk Labs
June 6, 2024 - In that case, they can replace any script that gets executed in subsequent steps with a malicious version, modify a configuration file with command execution potential (e.g., package.json used by npm install), or exploit a command injection vulnerability within a step to execute arbitrary code. The extent of the damage depends on how the permissions are configured and whether there are any secrets that can be leaked to compromise additional services. Since the GITHUB_TOKEN's lifecycle is limited to the currently running workflow, an attacker must craft the exploit to run within that window.