Skip to content

TIM - Update Recorded Future CVE risk label #40637

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

Open
wants to merge 13 commits into
base: master
Choose a base branch
from

Conversation

MosheEichler
Copy link
Contributor

@MosheEichler MosheEichler commented Jul 20, 2025

Status

  • In Progress
  • Ready
  • In Hold - (Reason for hold)

Related Issues

fixes: link to the issue

Description

we update the risk score labels according the recorded future changes in the CVE risk label.

Screenshots

image-2025-07-17-16-06-41-952

Must have

  • Tests
  • Documentation

@MosheEichler MosheEichler requested a review from Ni-Knight July 20, 2025 08:12
@MosheEichler MosheEichler self-assigned this Jul 20, 2025
Copy link

github-actions bot commented Jul 20, 2025

Coverage

Coverage Report
FileStmtsMissCoverMissing
Packs/FeedRecordedFuture/Integrations/FeedRecordedFuture
   FeedRecordedFuture.py2818171%78–79, 94, 108–110, 112, 114–115, 117, 119–122, 124, 126–127, 129–130, 142–143, 145, 152–154, 156–164, 170, 174–175, 177–182, 266–267, 317, 323–325, 349, 351–352, 354–357, 382, 400, 406, 426–434, 436, 461–463, 529, 598–602, 605–607
TOTAL2818171% 

Tests Skipped Failures Errors Time
53 0 💤 1 ❌ 0 🔥 3.332s ⏱️

@richardbluestone
Copy link
Contributor

Doc review done

@Ni-Knight
Copy link
Contributor

Ni-Knight commented Jul 20, 2025

Please add a description to the PR and state the changes.

Why are we changing it? It might break customer PB's I assume.

Seems like the ticket is for CVEs only, is it supposed to be general?

@MosheEichler MosheEichler changed the title Update RF verdict score TIM - Update Recorded Future CVE risk label Jul 21, 2025
@MosheEichler MosheEichler added the ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines label Jul 21, 2025
@MosheEichler MosheEichler enabled auto-merge (squash) July 21, 2025 20:15
@content-bot
Copy link
Collaborator

Validate summary
The following errors were thrown as a part of this pr: .
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.

Verdict: PR can be force merged from validate perspective? ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-approved ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants