-
Notifications
You must be signed in to change notification settings - Fork 1
Test fork PR scanning #26
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
base: master
Are you sure you want to change the base?
Conversation
Code ScanFork PR scanning is disabled by default. To scan this PR:
- uses: promptfoo/code-scan-action@v1
with:
enable-fork-prs: true |
|
@promptfoo-scanner-staging |
|
❌ Failed to trigger code scan. The workflow file |
|
@promptfoo-scanner-staging |
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.
👍 All Clear
I reviewed this PR for LLM security vulnerabilities across all six vulnerability classes (Prompt Injection, Data Exfiltration, PII/Secrets in Prompts, Insecure Output Handling, Excessive Agency, and Jailbreak Risks). The code is a traditional Express.js route handler with no LLM functionality or data paths.
Minimum severity threshold for this scan: 🟡 Medium | Learn more
|
@promptfoo-scanner-staging |
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.
👍 All Clear
This PR adds a test file for fork PR scanning. I reviewed the code changes and found no LLM security vulnerabilities. The code does not involve any LLM interactions, prompt construction, or agent capabilities.
Minimum severity threshold for this scan: 🟡 Medium | Learn more
Testing fork PR scanning with SQL injection vulnerability