Add non-execution security coverage for generated effect submissions#324
Open
Add non-execution security coverage for generated effect submissions#324
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Description
api/effects.test.tsthat POSTs aruntimeCodestring which would create a global side-effect if executed, then asserts the side-effect did not run and the server stored/returned the original code text.README.mdto explicitly document that moderation/generation endpoints only store/return code as text and do not run effect code on the server.Testing
npm test -- api/effects.test.tsand the test suite passed (20 testsall green).npm run docs:checkand the effects/transitions docs checks passed (4 testsall green).Codex Task