Skip to content
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

[backend/frontend] Implement the OpenBAS Implant (injector) for custom payloads (#1087) #1172

Merged
merged 5 commits into from
Jul 1, 2024

Conversation

SamuelHassine
Copy link
Member

Proposed changes

Copy link

codecov bot commented Jul 1, 2024

Codecov Report

Attention: Patch coverage is 37.64706% with 53 lines in your changes missing coverage. Please review.

Project coverage is 26.15%. Comparing base (922373f) to head (93c261c).

Files Patch % Lines
...ain/java/io/openbas/rest/injector/InjectorApi.java 0.00% 24 Missing ⚠️
...nbas/injectors/openbas/OpenBASImplantExecutor.java 9.09% 20 Missing ⚠️
...ors/openbas/model/OpenBASImplantInjectContent.java 0.00% 5 Missing ⚠️
...nbas/injectors/openbas/OpenBASImplantContract.java 75.00% 2 Missing ⚠️
.../io/openbas/injectors/openbas/OpenBASInjector.java 91.30% 2 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##             master    #1172      +/-   ##
============================================
+ Coverage     25.81%   26.15%   +0.33%     
- Complexity     1066     1081      +15     
============================================
  Files           481      485       +4     
  Lines         11714    11796      +82     
  Branches        630      635       +5     
============================================
+ Hits           3024     3085      +61     
- Misses         8600     8621      +21     
  Partials         90       90              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@SamuelHassine SamuelHassine merged commit 4f0629a into master Jul 1, 2024
6 checks passed
@SamuelHassine SamuelHassine deleted the feature/implant branch July 1, 2024 06:24
@Kedae Kedae added the filigran team use to identify PR from the Filigran team label Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
filigran team use to identify PR from the Filigran team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants