feat: Create a console reporter #44
Conversation
Phylum OSS Supply Chain Risk Analysis - INCOMPLETEThe analysis contains 1 package(s) Phylum has not yet processed, |
Codecov Report
@@ Coverage Diff @@
## main #44 +/- ##
==========================================
+ Coverage 44.00% 48.07% +4.07%
==========================================
Files 12 13 +1
Lines 400 441 +41
==========================================
+ Hits 176 212 +36
- Misses 223 228 +5
Partials 1 1
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 2 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
fix: Made the Config member of reporters public so it can be passed in
doc: Added a bit of documentation for the ConsoleReporter explaining its
current state
feat: Added a console icon for the Maven ecosystem
Phylum OSS Supply Chain Risk Analysis - SUCCESSThe Phylum risk analysis is complete and has passed the active policy. |
Phylum OSS Supply Chain Risk Analysis - INCOMPLETEThe analysis contains 6 package(s) Phylum has not yet processed, |
Phylum OSS Supply Chain Risk Analysis - SUCCESSThe Phylum risk analysis is complete and has passed the active policy. |
tarkatronic
force-pushed
the
feat/console-reporter
branch
from
a869d23
to
42d8a7c
Compare
Oh yes great call, we will have to include screenshots in our docs. My struggle is, I don't want to show our own vulnerabilities 😂 Maybe we can set up some kind of dummy org. That could also help with integration tests. But that's a super far future thing. 🤔 |
Fixes #33
This is a quick win that helps prove out the new multi-reporter interface.