Ci/build pipelines - #664
Merged
Merged
Conversation
- Added `monitor-build-egress.sh` script to detect and block unauthorized network egress during build processes. - Updated `package.json` to include new security commands for egress monitoring. - Modified `render.yaml` to run builds under the egress monitor with appropriate flags. - Enhanced `server/package.json` to integrate egress monitoring in the build process. - Cleaned up unused imports in `helpStore.ts`. - Updated global CSS file with a placeholder comment. - Added tests for the egress detection functionality, covering various scenarios including unauthorized connections and allowlist extensions.
- Implement tests for signature normalization, version classification, and internal member name checks. - Add tests for surface diffs, ensuring breaking and additive changes are correctly identified. - Introduce tests for evaluating drift with various scenarios, including major upgrades and exact pin requirements. - Create tests for parsing Cargo manifests and checking pinning requirements. - Include tests for extracting type surfaces from in-memory declaration files and real package installations. - Establish CLI tests for usage, error handling, and JSON output.
…ling - Implement tests for in-worker lockdown, ensuring restricted access to storage and globals. - Validate the boot process and message sanitization for zk and cluster worker schemas. - Test the creation and behavior of sandboxed workers with both same-origin and opaque iframe transports. - Ensure proper handling of message transferables and schema validation for inbound and outbound messages. - Integrate Vite plugin tests to confirm correct worker sandboxing behavior during development.
|
@Petrelid Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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
2 participants
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.
Summary
monitor-build-egress.sh blocks unauthorized network egress during builds (allowlisted hosts only); wired into package.json, server/package.json, and render.yaml build steps, with tests.
scripts/detect-api-drift.js diffs public API surfaces against checked-in baselines (npm, Cargo crates, TS declaration files), flags unreviewed breaking changes, and gates CI via a new api-drift-guard job. 43 tests, both security:api-drift* scripts pass RC=0.
Workers now launch from blob URLs created in a null-origin sandboxed iframe (src/lib/workerSandbox.ts + Vite post-transform plugin), with pre-import storage/DOM lockdown and strict zod message sanitization in both directions; fails open to a same-origin blob worker when opaque origin isn't viable. 47 tests, tsc/eslint/full-suite all at baseline.
Closes #595
Closes #597
Closes #598