# Security scanning of Julia code

**URL:** <https://discourse.julialang.org/t/security-scanning-of-julia-code/24253>\
**Category:** Tooling\
**Tags:** security\
**Created:** [May 15, 2019, 7:00pm UTC](https://discourse.julialang.org/t/security-scanning-of-julia-code/24253 "2019-05-15T19:00:21Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![oheil](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oheil/32/220745_2.png) [@oheil](https://discourse.julialang.org/u/oheil)\
**Post date:** [May 16, 2019, 1:10pm UTC](https://discourse.julialang.org/t/security-scanning-of-julia-code/24253/4 "2019-05-16T13:10:10Z")

</div>

There is a related discussion:

> [@Use a tool like Codacy to check common issues pattern](https://discourse.julialang.org/t/use-a-tool-like-codacy-to-check-common-issues-pattern/23855):
>
> Recently, I used Codacy on my fork of Julia, and [it discovered 936 issues](https://app.codacy.com/project/hossein_pourbozorg/julia/dashboard) (237 security + 36 error prone + 663 code style). So I think to suggest a discussion about “Use a tool like Codacy to check common issues pattern” for speed up issue discovering. I mark all issues pattern to check, so it leaves some ineffective issues. But if we configure it proper, it can be useful. [Screenshot%20from%202019-05-05%2002-43-13]

---

_[View the full topic](https://discourse.julialang.org/t/security-scanning-of-julia-code/24253)._