Skip to content

Forti shield patch 1 #2

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.

Sign up for GitHub

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

Merged
FortiShield merged 18 commits into from
Mar 8, 2025
Merged

Forti shield patch 1 #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
18 commits
Select commit Hold shift + click to select a range
f405e7f
Update .editorconfig
FortiShield Mar 8, 2025
b11459b
Update package.json
FortiShield Mar 8, 2025
c0a0364
Create npm_publish.yml
FortiShield Mar 8, 2025
2335b89
Update httpsnippet.ts
FortiShield Mar 8, 2025
1972068
Update nested.c
FortiShield Mar 8, 2025
4fde3bd
Update nested.cs
FortiShield Mar 8, 2025
a20ab6f
Update nested.cs
FortiShield Mar 8, 2025
d0594bc
Update nested.go
FortiShield Mar 8, 2025
473fdba
Update nested.java
FortiShield Mar 8, 2025
08d0782
Update nested.java
FortiShield Mar 8, 2025
ae3a3d2
Update nested.java
FortiShield Mar 8, 2025
b9c5468
Update nested.java
FortiShield Mar 8, 2025
0e2f46a
chore: decode full url
FortiShield Mar 8, 2025
fd7c7ba
Update sast.yml
FortiShield Mar 8, 2025
8650391
add: including the missing actions/upload-artifact@v3 step to ensure…
FortiShield Mar 8, 2025
fa448c3
Update src/targets/objc/nsurlsession/fixtures/nested.m
FortiShield Mar 8, 2025
9d48e2b
Update httpsnippet.ts
FortiShield Mar 8, 2025
b1f0ac1
Update .editorconfig
FortiShield Mar 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .editorconfig
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ indent_size = 2
end_of_line = lf
charset = utf-8
trim_trailing_whitespace = true
insert_final_newline = true
insert_final_newline = false

[targets/**/fixtures/*]
insert_final_newline = false
Expand Down
28 changes: 28 additions & 0 deletions .github/workflows/hopp-publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
name: Publish Package to NPM

on:
release:
types: [published]

jobs:
publish:
name: Publish
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v3

- name: Setup node
uses: actions/setup-node@v4
with:
node-version: 20
cache: 'npm'
registry-url: 'https://registry.npmjs.org'

- run: npm install
- run: npm run build

- name: Publish package
run: npm publish --access public
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
8 changes: 8 additions & 0 deletions .github/workflows/sast.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,3 +23,11 @@ jobs:
steps:
- uses: actions/checkout@v4
- uses: Kong/public-shared-actions/security-actions/semgrep@bd3d75259607dd015bea3b3313123f53b80e9d7f
with:
output: semgrep-results.json

- name: Upload Semgrep Report
uses: actions/upload-artifact@v3
with:
name: semgrep-results
path: semgrep-results.json
0 CONTRIBUTING.md → CONTRIBUTING.MD
View file
Open in desktop
File renamed without changes.
9 changes: 0 additions & 9 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,15 +4,6 @@

At HTTPSnippet, we take security issues very seriously. If you believe you have found a security vulnerability in our project, we encourage you to disclose it responsibly. Please report any potential security vulnerabilities to us by sending an email to [vulnerability@konghq.com](mailto:vulnerability@konghq.com).

## How to Report

1. **Do not publicly disclose the vulnerability**: Please do not create a GitHub issue or post the vulnerability on public forums. Instead, contact us directly at [vulnerability@konghq.com](mailto:vulnerability@konghq.com).
1. **Provide detailed information**: When reporting a vulnerability, please include as much information as possible to help us understand and reproduce the issue. This may include:
- Description of the vulnerability
- Steps to reproduce the issue
- Potential impact
- Any relevant logs or screenshots

## What to Expect

- **Acknowledgment**: We will acknowledge receipt of your vulnerability report within 48 hours.
Comment on lines 7 to 9
Copy link

@sourcery-ai sourcery-ai bot Mar 8, 2025

Choose a reason for hiding this comment

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

🚨 suggestion (security): Consider adding basic instructions for reporting vulnerabilities.

While the contact email is present, the removed "How to Report" section provided valuable guidance. Even brief instructions on what information to include in a report would be helpful. For example, suggest including a description, reproduction steps, and potential impact.

Suggested implementation:

## How to Report

When reporting a vulnerability, please include:
- A clear description of the issue
- Steps to reproduce the vulnerability
- The potential impact or severity of the issue
- Any relevant logs, screenshots, or supporting evidence (if available)

## What to Expect

If you have a specific contact email or additional reporting instructions elsewhere in the file, make sure to cross-reference or include it as needed.

Expand Down
Loading
Loading