ComponentsIssues
Runs Semgrep-based static analysis on software components to detect security vulnerabilities, insecure patterns, and code quality issues.HTTP Request Example
Response Format
Returns Semgrep findings grouped by component.components: List of analysed components with detected issuesstatus: Request execution result
purl: Component Package URLversion: Resolved component versionrequirement: Version constraint used for analysisfiles: Files containing detected issues
fileMD5: File hash for integrity trackingpath: File path within the componentissues: Detected Semgrep findings
ruleID: Semgrep rule identifierfrom: Starting line numberto: Ending line numberseverity: Issue severity (ERROR, WARNING, INFO)
Response Examples
Component with Security Issues
Component with No Issues Found
ComponentIssues
Runs Semgrep analysis on a single software component to identify security, quality, and compliance issues.HTTP Request Example
Response Format
Returns Semgrep findings for a single component.component: Analysed component resultstatus: Request execution result
purl: Component Package URLversion: Resolved versionrequirement: Version constraint used for analysisfiles: Files containing detected issues
Response Examples
Component with Security Issues
Component with No Issues Found
Security Analysis Coverage
Semgrep rules evaluate components across three areas:Security Vulnerabilities
- SQL injection patterns
- Cross-site scripting (XSS) vulnerabilities
- Command injection flaws
- Path traversal vulnerabilities
- Authentication and authorization bypasses
Code Quality Issues
- Hardcoded secrets and credentials
- Unsafe cryptographic practices
- Insecure random number generation
- Improper input validation
- Resource leaks and memory management issues
Compliance Rules
- OWASP Top 10 security risks
- CWE (Common Weakness Enumeration) categories
- Language-specific security anti-patterns
- Framework-specific security misconfigurations
Supported Languages
- Java