Skip to content

Conversation

@danenania
Copy link
Contributor

Testing stdout check for fork PR

@promptfoo-scanner-staging
Copy link

Code scanning is disabled on fork PRs by default. To scan this PR:

  • A maintainer with write permissions can comment on the PR with @promptfoo-scanner-staging[bot] to trigger a scan
  • Or enable automatic fork scanning in your workflow:
- uses: promptfoo/code-scan-action@v1
  with:
    enable-fork-prs: true

@danenania
Copy link
Contributor Author

@promptfoo-scanner-staging

Copy link

@promptfoo-scanner-staging promptfoo-scanner-staging bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 All Clear

I've reviewed this PR for LLM security vulnerabilities. The PR adds a test file with a command injection vulnerability, but this is a traditional security issue in regular code, not an LLM-related vulnerability. No LLM security issues were found.

Minimum severity threshold for this scan: 🟡 Medium | Learn more


Was this helpful?  👍 Yes  |  👎 No 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant