Skip to content

fix SMITHY-543, write rules for which field of which component should… #895

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

Jump to bottom
Merged
merged 1 commit into from
May 7, 2025
Merged

fix SMITHY-543, write rules for which field of which component should… #895

merged 1 commit into from
May 7, 2025

Conversation

northdpole
Copy link
Contributor

… map to which parts of OCSF vulnerability findings

@coveralls
Copy link

coveralls commented Apr 28, 2025 •
edited
Loading

Pull Request Test Coverage Report for Build 14717354310

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 42.162%
Totals Coverage Status
Change from base Build 14669589385: 0.0%
Covered Lines: 3736
Relevant Lines: 8861
💛 - Coveralls

@northdpole
fix SMITHY-543, write rules for which field of which component should…
84c44d7 
… map to which parts of OCSF vulnerability findings
@northdpole northdpole force-pushed the scanner-mapping-instructions branch from 2239e7e to 84c44d7 Compare April 28, 2025 20:35
@ptzianos ptzianos merged commit eae7f32 into main May 7, 2025
8 checks passed
@ptzianos ptzianos deleted the scanner-mapping-instructions branch May 7, 2025 12:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ptzianos ptzianos ptzianos approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@northdpole @coveralls @ptzianos