How aquilax-ai/findings works
Project type and purpose
• This is not a running web or microservice application but a “Test Data Repository” whose sole purpose is to host vulnerable code and configuration examples.
• It’s used to validate and benchmark security‐scanning tools (e.g., Aquilax) across categories such as SAST, PII, Secrets, SCA (dependency scanning), IaC scanning, container security, malware detection, and mobile app vulnerabilities.
File structure
• Top‐level:
• .github/workflows/text.yml → CI orchestration via GitHub Actions
• FP/ → False‐positive test cases
• TP/ → True‐positive (actual vulnerable) test cases
• Root sample manifests: Dockerfile, package.json, pom.xml, requirements.txt (SCA targets)
• Under both FP/ and TP/: six main subfolders:
• IAC (Kubernetes YAML, Terraform)
• Malware (code in C, Go, PHP, Python, Java, etc.)
• PII (text files with fake PII)
• SAST (scripts and source illustrating injection, XSS, SSRF, etc.)
• SECRETS (hardcoded keys, env vars)
• Mobile (only in TP – an iOS Xcode project with insecure code examples)
README for additional insights
• Lists every category of vulnerability covered (SQLi, XSS, CSRF, IDOR, XXE, insecure Docker, outdated deps, etc.)
• Describes a simple usage flow: clone repo → run scanners → review findings