Allen D. Householder
Allen D. Householder
See also #17 which talks about splitting the data into a separate repository from the code that generates it. It's probably a good idea to consider either doing #1 and...
Fixing this might also address #7 and possibly provide an opportunity to address #10.
Also related is #17
We're looking into this within the context of our work on [Vultron](https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=887198&_gl=1*1jgb9g5*_ga*MTIxOTA3MTQ2Ny4xNjY0MTk5MTk2*_ga_87WECW6HCS*MTY2NDE5OTE5NS4xLjEuMTY2NDIwMDkxMy4wLjAuMA..).
Waiting for scheduled run to see if it's fixed. Check for runs >8210 on https://github.com/CERTCC/labyrinth/actions/workflows/repo_search.yml
Check https://github.com/CERTCC/labyrinth/actions/runs/6578349678 and close if success
This has succeeded since then, so it's safe to conclude it's fixed.
also happened in https://github.com/CERTCC/labyrinth/actions/runs/5510599382/job/14918209014
Hi, I'm working this through our legal folks, so I don't have a definitive answer at the moment. However, I can say that our intent was that: - Code is...
> I am assuming your concern is to keep the integrity of the SSVC specification and avoid derived work that would be still pretend to be SSVC? I am sure...