Allen D. Householder
Allen D. Householder
Expanding on: - #289 - #388 - #445 It seems like we should consider versioning Outcome sets as well. This seems like a relatively easy thing to clone from what...
We have a number of decision point groups defined in the code, and we should provide documentation similar to that for decision points for each of them. This will involve...
**Describe the bug** We have an action on the staging repo that syncs with this repo on a schedule. It should trigger the deploy_site action in that repo as well,...
> We will create a breadcrumb issue for us to revisit versioning policy later. _Originally posted by @ahouseholder in https://github.com/CERTCC/SSVC/issues/500#issuecomment-1967505057_ Summarizing discussion around #500: - Now that we have versioning...
This issue could be made redunant by a solution to - #482 Otherwise, at present, we have HTML content in the description of the Safety decision point following the merge...
We have multiple pages in the Reference section covering the various Decision Points. We recently added a number of outcome sets to the Python code, and that is documented in...
We currently have a separate tool `doctools.py` that generates a bunch of `.md` and `.json` files for the various decision points, outcome sets, etc. This works ok, assuming we remember...
Add docs for all the things added by #377
Inspired by CERTCC/Vultron#6, as well as with a similar goal of integration as #314, we should create a document explaining how SSVC and CVSSv4 intersect/overlap. As in #314, I think...
We are currently using `markdownlint-cli2` in CERTCC/Vultron to automate reformatting of markdown files for consistency. We should have a workflow action that runs against PRs that will only pass when...