Skip to content

feat(ci): Add security vulnerability skill action#19355

Draft
nicohrubec wants to merge 3 commits intodevelopfrom
nh/automatie-security-skill
Draft

feat(ci): Add security vulnerability skill action#19355
nicohrubec wants to merge 3 commits intodevelopfrom
nh/automatie-security-skill

Conversation

@nicohrubec
Copy link
Member

No description provided.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 17, 2026

Codecov Results 📊


Generated by Codecov Action

@github-actions
Copy link
Contributor

Codecov Results 📊

23 passed | ⏭️ 7 skipped | Total: 30 | Pass Rate: 76.67% | Execution Time: 12.25s

📊 Comparison with Base Branch

Metric Change
Total Tests
Passed Tests
Failed Tests
Skipped Tests

✨ No test changes detected

All tests are passing successfully.


Generated by Codecov Action

@github-actions
Copy link
Contributor

size-limit report 📦

Path Size % Change Change
@sentry/browser 25.56 kB - -
@sentry/browser - with treeshaking flags 24.08 kB - -
@sentry/browser (incl. Tracing) 42.36 kB - -
@sentry/browser (incl. Tracing, Profiling) 47.03 kB - -
@sentry/browser (incl. Tracing, Replay) 81.18 kB - -
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags 70.8 kB - -
@sentry/browser (incl. Tracing, Replay with Canvas) 85.87 kB - -
@sentry/browser (incl. Tracing, Replay, Feedback) 98.03 kB - -
@sentry/browser (incl. Feedback) 42.29 kB - -
@sentry/browser (incl. sendFeedback) 30.23 kB - -
@sentry/browser (incl. FeedbackAsync) 35.22 kB - -
@sentry/browser (incl. Metrics) 26.74 kB - -
@sentry/browser (incl. Logs) 26.88 kB - -
@sentry/browser (incl. Metrics & Logs) 27.56 kB - -
@sentry/react 27.33 kB - -
@sentry/react (incl. Tracing) 44.72 kB - -
@sentry/vue 30.01 kB - -
@sentry/vue (incl. Tracing) 44.22 kB - -
@sentry/svelte 25.58 kB - -
CDN Bundle 28.11 kB - -
CDN Bundle (incl. Tracing) 43.2 kB - -
CDN Bundle (incl. Logs, Metrics) 28.95 kB - -
CDN Bundle (incl. Tracing, Logs, Metrics) 44.03 kB - -
CDN Bundle (incl. Replay, Logs, Metrics) 68.02 kB - -
CDN Bundle (incl. Tracing, Replay) 80.07 kB - -
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) 80.94 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback) 85.5 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) 86.4 kB - -
CDN Bundle - uncompressed 82.22 kB - -
CDN Bundle (incl. Tracing) - uncompressed 127.93 kB - -
CDN Bundle (incl. Logs, Metrics) - uncompressed 85.05 kB - -
CDN Bundle (incl. Tracing, Logs, Metrics) - uncompressed 130.76 kB - -
CDN Bundle (incl. Replay, Logs, Metrics) - uncompressed 208.71 kB - -
CDN Bundle (incl. Tracing, Replay) - uncompressed 244.81 kB - -
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) - uncompressed 247.63 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 257.61 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) - uncompressed 260.42 kB - -
@sentry/nextjs (client) 47.07 kB - -
@sentry/sveltekit (client) 42.81 kB - -
@sentry/node-core 52.16 kB +0.02% +9 B 🔺
@sentry/node 166.54 kB +0.01% +9 B 🔺
@sentry/node - without tracing 93.96 kB +0.02% +12 B 🔺
@sentry/aws-serverless 109.46 kB +0.01% +9 B 🔺

View base workflow run

@github-actions
Copy link
Contributor

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario Requests/s % of Baseline Prev. Requests/s Change %
GET Baseline 9,372 - 11,206 -16%
GET With Sentry 1,641 18% 1,856 -12%
GET With Sentry (error only) 6,154 66% 7,570 -19%
POST Baseline 1,192 - 1,166 +2%
POST With Sentry 587 49% 572 +3%
POST With Sentry (error only) 1,049 88% 1,025 +2%
MYSQL Baseline 3,230 - 3,984 -19%
MYSQL With Sentry 474 15% 515 -8%
MYSQL With Sentry (error only) 2,664 82% 3,288 -19%

View base workflow run

Comment on lines +36 to +38
IMPORTANT: Do NOT dismiss any alerts. Do NOT wait for approval.
Create a branch, apply the fix, and open a PR with your analysis
in the PR description. Target the develop branch.
Copy link
Member

Choose a reason for hiding this comment

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

Just wondering what we should do in case the alert should be dismissed. Create an issue that informs us?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah right now it would create a PR with an explanation why the alert should be dismissed, an issue is probably more appropriate in that case

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.

2 participants