You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary: OWASP has a ton of projects which are very fragmented across both org repos and random github repos. Each project performs it's own tasks but there's no centralized way of finding what each project does and how it connects to the rest.
This can be solved by adding a small metadata file to each project root.
Then we can use Github's api to either search for specific strings in the metadata files or, grab the metadata files from the owasp org and statically map owasp projects not under the org.
From there a script can extract metadata and populate a template with:
State of SDLC each project fits in,
Links to github and docs
Builders Breakers Defenders designation
This allows central presentation of all owasp projects and ease of finding new ones.
Metadata file format TBD.
Acceptance Criteria:
There's an automated way to gather info about owasp projects and presenting them.
There is a way to see info about flagship projects in one place.
The text was updated successfully, but these errors were encountered:
Summary: OWASP has a ton of projects which are very fragmented across both org repos and random github repos. Each project performs it's own tasks but there's no centralized way of finding what each project does and how it connects to the rest.
This can be solved by adding a small metadata file to each project root.
Then we can use Github's api to either search for specific strings in the metadata files or, grab the metadata files from the owasp org and statically map owasp projects not under the org.
From there a script can extract metadata and populate a template with:
This allows central presentation of all owasp projects and ease of finding new ones.
Metadata file format TBD.
Acceptance Criteria:
The text was updated successfully, but these errors were encountered: