-
Notifications
You must be signed in to change notification settings - Fork 12
What do we want to do in 2025? #26
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
Comments
On the supply chain security/transparency track, I'm thinking of how we can adapt SLSA for ML. We can build on top of model signing, sign datasets, create SLSA-aware ML training pipelines that practitioners can use with minimal changes to their workflows |
Andrey Shorov, Elif Soykan and I want to produce the following (with the rest of the WG help fi you'd all like):
|
Something that came up in the Model Signing SIG, that is out of scope of the SIG, but could be an output of the AIML WG: provide input on model card metadata. Potential sync with Open Oasis Data Provenance standard, LF Model Openness Framework, and CosAI RFC Supply Chain work group |
Do we/should we have any advice for developers leveraging deepseek.ai to apply OpenSSF tools/concepts for security? |
I like both of these ideas! |
What does a security model of an agentic architecture look like? Much of this is OSS in the tool chain: langchain, langgraph/knowledge graphs, APIs. Where are their architecture choices developers and enterprises may need to understand that introduce more risk/opportunity for compromise? |
Please add your ideas here so the group can create distinct issues for items we choose to pursue.
“definition of done” is when individual issues have been created and prioritized.
Please have any additional items added here by January 19th 2025
The text was updated successfully, but these errors were encountered: