qaz@lemmy.world to Programmer Humor@programming.devEnglish · 1 day agoSeCurItY IsSuElemmy.worldimagemessage-square9fedilinkarrow-up1228arrow-down10file-text
arrow-up1228arrow-down1imageSeCurItY IsSuElemmy.worldqaz@lemmy.world to Programmer Humor@programming.devEnglish · 1 day agomessage-square9fedilinkfile-text
minus-squareinari@piefed.ziplinkfedilinkEnglisharrow-up34·1 day agoWhat was the issue? Without looking at the PR it’s hard to judge
minus-squareHeHoXa@lemmy.ziplinkfedilinkarrow-up1·9 minutes agoNot being sure it applies to this scenario and too lazy to verify, sometimes the security scanners get updated and flag previously accepted code. … tough to make sense of flagging a readme though, unless there’s sensitive info in it.
minus-squarebalsoft@lemmy.mllinkfedilinkarrow-up36·1 day agoThe link in the comment is borked, as expected. But the PR itself is definitely OK: https://github.com/unipop-graph/unipop/pull/138
What was the issue? Without looking at the PR it’s hard to judge
Not being sure it applies to this scenario and too lazy to verify, sometimes the security scanners get updated and flag previously accepted code.
… tough to make sense of flagging a readme though, unless there’s sensitive info in it.
it’s a readme change
It was a load-bearing readme file.
The link in the comment is borked, as expected. But the PR itself is definitely OK: https://github.com/unipop-graph/unipop/pull/138