| title | displaytext | layout | tab | order | tags |
|---|---|---|---|---|---|
Join |
Join |
true |
2 |
nocode |
Involvement in the development and promotion of OWASP Top 10 Low-Code/No-Code Security Risks is actively encouraged! You do not have to be a security expert in order to contribute.
Here are some ways you can help:
- We are looking for organizations and individuals that will provide vulnerability prevalence data
- Translate the top 10 to non-English languages
- Review, critic and suggest improvements to the Top 10 list
Individuals and organizations that provide a significant contribution to the project will be listed on the acknowledgments page.
- Give us feedback / suggestions / report bugs on GitHub
- Join our email group
- Contact the project leads
- Talk to us on Slack (#low-code-no-code-top10-security-risks)
Got any ideas on how to make this project better? These guidelines could help make things clearer going forward.
- Join the conversation on email or Slack to find collaborators or see if others have a similar interest.
- Search the project's GitHub issues for related proposals. Found one? Join it!
- If you haven't found a relevant issue, create one! Clearly specify why your proposal is important and which changes are proposed. Advertise your proposal to others to find collaborators. See examples: Add descriptions for business users, Add product-specific examples.
- Create an initial draft implementing your proposal and submit it for review as a PR. Don't let perfect be the enemy of good.
- Advertise your proposal to others and ask for reviews.
- Once your PR is merged, continue to submit PRs to fine-tune and improve on previous versions.
- Congrats and thank you!