Maturity-Models
Maturity-Models copied to clipboard
OWASP
Node application to help managing Maturity Models like the ones created by BSIMM and OpenSAMM
Will help to detect current deployed version and release time
At the moment it is on activity-table.css file 
for example data can be stored as a percentage on the YES value ``` coffee { "metadata": { "team": "Team A" }, "activities": { "Governance": { "SM.1.1": "Yes:100", "SM.1.4": "Yes:30",...
This will make the process smother and not require regular submodule sync commits on base repo (only doing those commits on release, not on bug fix)
This would allow the consolidation of teams data and results Handles the case where a particular project will have more than one sub-project which requires a Maturity Model in its...
Add support for renaming teams inside a project This has some security implications due to path injection on rename value
So that they are not mis-aligned 
after save  after refresh 
Start with this one and then evolve it into more custom scans Check if these scans show up in logs
This tests is currently checking the status of the pages when the menus are clicked and it is not very stable ``` coffee # todo: this test is not very...