JohnVonNeumann/opensorcery

Implement secrets checking via githooks and the CI.

Open

#36 opened on Apr 14, 2019

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (0 forks)auto 404
2POINTERdeveloper-productivitydevopsenhancementgood first issuehelp wantedsecurity

Repository metrics

Stars
 (7 stars)
PR merge metrics
 (PR metrics pending)

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.

Contributor guide

Research direction
Research and integrate a tool like git secrets (https://github.com/awslabs/git secrets) as a pre commit hook and in the CI pipeline to block commits with potential secrets. Ensure it scans staged changes and runs on every push.
Tech stack
javascript
Domain
securityci cd
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitCI basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60