cypht-org/cypht

Security Audit

Open

#366 opened on Dec 27, 2019

View on GitHubContributor guide
 (8 comments) (0 reactions) (0 assignees)PHP (226 forks)auto 404
help wanted

Repository metrics

Stars
 (1,660 stars)
PR merge metrics
 (PR metrics pending)

Description

🗣 Suggestion

As discussed already before in https://github.com/jasonmunro/cypht/issues/11#issuecomment-283608217 , a security audit would be beneficial. Today I heard about Google Patch Rewards extending their offering to all open source projects. Cypht could try to apply :wink:.

Contributor guide

Research direction
Research the project's current security measures, identify potential areas for a security audit, and propose a plan for applying to Google Patch Rewards. Review the previous discussion linked in the issue.
Tech stack
phpjavascript
Domain
backendsecurity
Issue type
Research
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.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30