Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated readme: added OWASP WrongSecrets #552

Merged
merged 2 commits into from
Jun 21, 2022
Merged

Conversation

commjoen
Copy link
Contributor

Your Project

OWASP WrongSecrets

1Password Teams URL

https://owasp.1password.com/home

Project Name

OWASP Wrongsecrets

Short Description

OWASP WrongSecrets is the first Secrets Management-focused vulnerable/p0wnable app! It can be used in security trainings, awareness demos, as a test environment for secret detection tools, and bad practice detection tooling.

Project Age

6 months

Number Of Core Contributors

3

Project Website

https://owasp.org/www-project-wrongsecrets/

Repository URL(s)

https://github.com/commjoen/wrongsecrets
https://github.com/commjoen/wrongsecrets-binarys
https://github.com/OWASP/www-project-wrongsecrets

Latest Release URL(s)

https://github.com/commjoen/wrongsecrets/releases

License Type

MIT

License URL

https://github.com/commjoen/wrongsecrets/blob/master/LICENSE

A Bit About Yourself

I am one of the 2 project leaders of OWASP WrongSecrets, before that I have been active in various OWASP Projects.

Name

Jeroen Willemsen

Email

jeroen.willemsen@owasp.org

Project Role

Proeject leader

Profile/Website

https://github.com/commjoen/

Comments

We would like to use this account to create a blocked user with a recovery package, which we then can commit to git so that secret scanners in git know where to look for to revoke this.

@jodyheavener jodyheavener added the deprecated/approved This application has been approved label Jun 21, 2022
@jodyheavener
Copy link
Member

Thanks for your application, @commjoen! I've gone ahead and applied the promotion to your account.

If you haven't done so already, I would definitely recommend implementing a recovery plan for your team in case access for a particular contributor is ever lost. You are also welcome to add additional core contributors as you see fit.

Also, we'd love to hear more about your experience using 1Password in your development workflows! Feel free to join us over on the 1Password Developers Slack workspace 🙂

@jodyheavener jodyheavener merged commit eb27c84 into 1Password:main Jun 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deprecated/approved This application has been approved
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants