Run Semgrep, Trivy, osv-scanner, and Bandit to identify security vulnerabilities.
npx skills add https://github.com/jiayaoqijia/eth2030 --skill scan-jiayaoqijia
Please help me install this Agent Skill. Skill: scan Source: https://github.com/jiayaoqijia/eth2030/tree/main/.claude/skills/scan Command: npx skills add https://github.com/jiayaoqijia/eth2030 --skill scan-jiayaoqijia
Run consolidated security scans across multiple engines to identify vulnerabilities in a codebase and produce a structured report.
Run a security scan on the current project directory and return a structured report.
High-intent search queries and answers about installing and using this skill.
To run a security vulnerability scan on a codebase, you can execute Semgrep, Trivy, osv-scanner, and Bandit in parallel across a target directory. This consolidates findings into a single structured report with severities and OWASP mappings.
Yes, you can integrate multi-engine codebase security scanning into CI pipelines to fail builds on critical findings. The scanners produce a machine-readable JSON report that can be evaluated by CI rules or exported to a dashboard for triage.
The best way to identify OWASP vulnerabilities in a code repository is running a unified scan across multiple engines like Semgrep and Bandit. This approach surfaces diverse vulnerabilities and aligns them with OWASP categories in a structured JSON report.
Unified security scanning supports engine-specific runs across languages and package ecosystems. You can target a specific directory or repository for a full scan, or isolate the execution to individual engines where applicable.
Parallel security scanning generates structured reports by running Semgrep, Trivy, osv-scanner, and Bandit concurrently, then aggregating the results. The output is a machine-readable JSON file containing severity mappings, file paths, and OWASP alignments.
Using multiple codebase scanners like Semgrep, Trivy, osv-scanner, and Bandit surfaces a wider range of vulnerabilities across different languages and package ecosystems. This consolidated approach ensures broader security coverage and structured OWASP-aligned reporting.
Generous-CorpManage local Pulp-native artifact lifecycles with filesystem safety and trust boundaries.
openshift-engParse Prow CI audit and pod logs to generate interactive HTML resource timelines.
yu-iskwAudits security vulnerabilities using Trunk CLI, Trivy and OSV-scanner.
hpsgdIdentifies vulnerabilities, outdated packages, and licensing risks in project dependencies.
