JohnVonNeumann/opensorcery

Implement secrets checking via githooks and the CI.

Aberta

#36 aberto em 14 de abr. de 2019

 (0 comentário) (0 reação) (0 responsável)JavaScript (0 fork)auto 404
2POINTERdeveloper-productivitydevopsenhancementgood first issuehelp wantedsecurity

Métricas do repositório

Stars
 (7 estrelas)
Métricas de merge de PR
 (Métricas PR pendentes)

Description

Is your feature request related to a problem? Please describe. Secrets disclosure is a massive security hole, with a disproportionate number of breaches being a direct result of secrets being exposed.

Describe the solution you'd like

I want a simple solution that checks all code for secrets and manages the rejection of potentially dangerous code/additions. Preferably at both the client side and server side.

Describe alternatives you've considered A solution such as https://github.com/awslabs/git-secrets would suit well. I have not looked at other items. This would be great via githooks and also within the CI process.

Guia do colaborador