JohnVonNeumann/opensorcery

Implement secrets checking via githooks and the CI.

Offen

#36 geöffnet am 14.04.2019

 (0 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)JavaScript (0 Forks)auto 404
2POINTERdeveloper-productivitydevopsenhancementgood first issuehelp wantedsecurity

Repository-Metriken

Stars
 (7 Sterne)
PR-Merge-Metriken
 (PR-Metriken ausstehend)

Beschreibung

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.

Contributor Guide