-
Notifications
You must be signed in to change notification settings - Fork 15
Updating to accept changes in the upstream repo #19
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: feature/update-from-upstream
Are you sure you want to change the base?
Updating to accept changes in the upstream repo #19
Conversation
fix(bin) wrong path to ValidationError module
obj-c and swift used to not handle converting boolean values to their respective literal notation. Fix #65
Add option to include boilerplate
fix(obj-c + swift) handling boolean literal values
… the final boundary
- update testing method to remove reliance on `require-directory` - require-directory is now a `devDependency`
standard
Add option for --data-binary flag in curl
* fix: tag weirdness * fix * fix * fix
* Create initial rust files Create initial rust files to support the target. Create all of the demo fixture files for the different request types. These also require specific `Cargo.toml` dependencies with some features, but I've tried to keep them fully qualified where possible. I'm not sure yet how best to show adding dependencies to a project to enable these features. * Start work on reqwest client Start working on the reqwest conversion client after adding targets. * Complete Adding Rust as target Completed adding Rust as a target. All of the fixtures have been tested in a separate Rust project to verify that they build and successfully run against the Har test endpoint. All tests are running and passing, except for the snapshot that verifies all available targets, not sure where to update that. * Run linter Ran the linter defined in `package.json` All tests except snapshot for targets passing. * Update snapshot to fix available targets test Update the available targets test to fix the snapshot. * lint --------- Co-authored-by: Filipe Freire <[email protected]>
Bumps [ws](https://github.com/websockets/ws) from 7.5.7 to 7.5.10. - [Release notes](https://github.com/websockets/ws/releases) - [Commits](websockets/ws@7.5.7...7.5.10) --- updated-dependencies: - dependency-name: ws dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [braces](https://github.com/micromatch/braces) from 3.0.2 to 3.0.3. - [Changelog](https://github.com/micromatch/braces/blob/master/CHANGELOG.md) - [Commits](micromatch/braces@3.0.2...3.0.3) --- updated-dependencies: - dependency-name: braces dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [@babel/traverse](https://github.com/babel/babel/tree/HEAD/packages/babel-traverse) from 7.22.6 to 7.24.5. - [Release notes](https://github.com/babel/babel/releases) - [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md) - [Commits](https://github.com/babel/babel/commits/v7.24.5/packages/babel-traverse) --- updated-dependencies: - dependency-name: "@babel/traverse" dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Generate Crystal language code * Generate Crystal language code * Remove a blank line * fix crystal tests --------- Co-authored-by: Filipe Freire <[email protected]>
* fix: prevent override of default value of request.postData when postData might be undefined * chore: optional chaining safety check for when request.PostData can be undefined
* Support any method for PowerShell * fix test --------- Co-authored-by: Filipe Freire <[email protected]>
* Add nvmrc and set it to 14.9 as per #248 * Use node 18 * bump to node 20 on nvmrc file --------- Co-authored-by: Filipe Freire <[email protected]>
Co-authored-by: Lukas_Skywalker <[email protected]>
* updates library exports * fixes lint configuration so that it actually fails now, as intended * tidy up --------- Co-authored-by: Filipe Freire <[email protected]>
* Feat: replace custom har-validator with hard-validator-compiled package * test(http-snippet): update casing * fix: linting
Ensure that code snippets use enum members that are pascal cased and not upper cased. For example use `Method.Get` instead of `Method.GET` to ensure the snippets can compile. fixes #365 use `var` for return "type" of RestSharp request response The type `IRestResponse` doesn't exist in latest client (version 112) fixes #367
* fix(form-data): override import from package root * fix(httpsnippet): linting errors
…HAs (#378) * Pin all external github actions to their corresponding commit SHAs * Update security actions to use the latest commit
| @@ -0,0 +1,9 @@ | |||
| # specify the node base image with your desired version node:<version> | |||
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.
Missing User Instruction
on resource FROM node:8 AS node:8
More Details
This rule checks whether a `USER` instruction is specified in the Dockerfile. The rule fails when the `USER` instruction is missing, causing the container to run with root privileges (UID 0). If an attacker compromises an application running as root, they gain the privileges needed to potentially escape the container and attack the host node. It also increases the blast radius of a breach, allowing full control to modify files or install malware within the container. Enforcing a non-root user is a fundamental security measure that minimizes the attack surface and contains the impact of a potential compromise.
Expected
The Dockerfile stage should contain the 'USER' instruction
Found
The Dockerfile stage does not contain any 'USER' instruction
Rule ID: 4551f6ed-2d6d-405a-9bc0-3e3559364f23
To ignore this finding as an exception, reply to this conversation with #wiz_ignore reason
If you'd like to ignore this finding in all future scans, add an exception in the .wiz file (learn more) or create an Ignore Rule (learn more).
To get more details on how to remediate this issue using AI, reply to this conversation with #wiz remediate
Related - postmanlabs/postman-app-support#1475