I replaced nsp (out of date badge), with Snyk to show the known vulnerabilities status for the project.
Would be great to see the project adds a GitHub integration too with Snyk to make sure no new changes are introducing security risks and newly disclosed vulnerabilities for dependencies used here will be monitored :-)
Coverage remained the same at 99.515% when pulling 89581bb41f2b66a61d859e8310cdb082cbe25122 on lirantal:patch-1 into fc13de682aa462f98c921c56aaec7f2f641622ee on Zooz:master.
Coverage remained the same at 99.515% when pulling 89581bb41f2b66a61d859e8310cdb082cbe25122 on lirantal:patch-1 into fc13de682aa462f98c921c56aaec7f2f641622ee on Zooz:master.
I replaced nsp (out of date badge), with Snyk to show the known vulnerabilities status for the project. Would be great to see the project adds a GitHub integration too with Snyk to make sure no new changes are introducing security risks and newly disclosed vulnerabilities for dependencies used here will be monitored :-)