Add SocketDev workflow for firewall-free mode - #13286
HackingRepo wants to merge 4 commits into
Conversation
|
@cakebaker can you take a look in that? i appreciate it |
|
GNU testsuite comparison: |
|
hi, @cakebaker can you take a look in that and merge it and review it? i appreciate it |
|
hi, @sylvestre can you review that pr, i appreciate it, and thank's for your effort |
|
Sorry but I don't understand this PR. I don't know what is socketdev |
|
read https://github.com/SocketDev/action to see, the meaning, i mean socket firewall, @sylvestre the explanation i can say, by example someone add a new dep or crate or whatever callled, socket firewall will evaluate the supply chain security score and maintenance score and quality and license and vulnerability and also for renovabot update, if any crate of one used ever compromised and ships malware socket firewall will say supply chain security very low score and then that was a malware incident if the score 75% or heigher then safe to merge |
Merging this PR will not alter performance
Comparing Footnotes
|
97fc464 to
9e0defe
Compare
|
I am still unfortunately not very convinced by this |
|
why it is important for supply chain security since the repo have no pinning, a supply chain attack in these deps since uutils use dozens of deps, if just one compromised, then these utilities will serve malware? |
| @@ -0,0 +1,14 @@ | |||
| on: push | |||
There was a problem hiding this comment.
why only push and not pull_request? renovate PRs are the stated use case
|
|
||
| - uses: SocketDev/action@v1.3.1 | ||
| with: | ||
| mode: firewall-free |
There was a problem hiding this comment.
what does firewall-free mean here? please document the why
There was a problem hiding this comment.
@sylvestre, The term firewall-free (short for Socket Firewall Free) refers to the Free Edition of Socket's security tool. It means zero-configuration and entirely free security, requiring no API keys, no secrets management, and no account sign-ups to run in this repository.
Hi, i did that because i see mainteners merge dependabot prs just in hours, if there was a supply chain incident then will progogate by using https://socket.dev, because mainteners a lot frustrated by pinning actions and merge a renovabot pr after days, instead that is the solution a maintener can merge an update safely using that, very easy it outputs the supply chain score in curcilar graph, to see is the update safe or no, before merging, i finally retrieved a solution for that repo, since mainteners frustrated by classical supply chain defenses like pinning deps and github actions and do'nt merge a renovabot pr before 1 day, that was actually frustrating that will be optimal for mainteners while maintening supply chain security
5d9d981 to
a8b587f
Compare
Hi, i did that because i see mainteners merge renovabot prs just in hours, if there was a supply chain incident then will progogate, because mainteners a lot frustrated by pinning actions and merge a renovabot pr after days, instead that is the solution a maintener can merge an update safely using that, very easy it outputs the supply chain score in curcilar graph, to see is the update safe or no, before merging, i finally retrieved a solution for that repo, since mainteners frustrated by classical supply chain defenses like pinning deps and github actions and do'nt merge a renovabot pr before 1 day, that was actually frustrating that will be optimal for mainteners while balancing and maintening supply chain security for free no cost and usability too