Ignacio Dominguez

Please let me know if any changes are required to improve this check. I'm not a very experienced prowler user so apologies in advanced if I'm not following any best...

Hi @sergargar thanks for your changes. What kind of packages are you experiencing ORIGIN_TYPE=None? From what I see in AWS docs it should always be INTERNAL or EXTERNAL. > originType...

I see, how did you create that package I'll try to replicate it. I've tested this in an org with over 50k package versions (pip, mvn and npm) and I've...

I found a package that also has no origin info this is how it looks like in the AWS console.  It is slightly different from your example  I...

My python test packages were pushed to codeartifact in the same way you did it. I might be able to get in touch with someone from AWS's code artifact development...

I just heard back from AWS: There are two things here. The fact that originType is UNKNOWN is expected for packages that were added to CodeArtifact before we released the...

AWS believe this is probably due to you AWS CLI version you will need to be using at least v2.7.16. Let me know if that fixes it for you and...