| Blog | https://mihai.page |
| Blog | https://mihai.page |
Now, there is some time to reflect and determine what are the next steps to be taken in this space to increase impact. I might have already hinted at some, but next year's conference talks will be about them :)
Thankful again for the entire community! Remember that we need to ensure now that the intelligent creations we are now making with AI don't become the security nightmares of tomorrow.
Heading to #PyTorchCon 2025? Donβt miss our BoF on Applying DevSecOps Lessons to MLSecOps (Oct 23 | 10:30 AM PDT).
Join Jeff Diecks + @mihaimaruseac as we explore secure AI/ML development with the OpenSSF AI/ML Security WG.
> Vibe coding with AI is cool until you get hacked :)
Here are 3 different resources that can help with that, all developed by amazing people at the @openssf AI/ML working group and other OpenSSF WGs.
First, https://openssf.org/blog/2025/09/16/new-openssf-guidance-on-ai-code-assistant-instructions/ is an exceptional guidance on using AI for writing code securely.
Next, a Tech Talk about a secure ML lifecycle: https://openssf.org/resources/tech-talks/securing-the-ai-lifecycle-trust-transparency-tooling-in-open-source/
Finally OpenSSF will soon launch a new @linuxfoundation course, LFEL1012, on using AI coding assistants. Stay tuned!
A Pythagoreic date like today's only occurs once a century
>>> for m in [1,2,3]:
... for d in [1,2,3,4,5]:
... y=m**2 + d**2
... y_sq=int(math.sqrt(y))
... if y_sq * y_sq==y:
... print(f"{m**2}/{d**2}/20{y}")
...
9/16/2025
At the beginning of the year I wanted to compare models and prompt techniques on several math problems. I also got a common sense one. Today I publish the last article in the series, where I use a vibe-coded Colab to analyze which models are better than others and which prompt techniques are useful.
This blog introduces PyTrees β nested Python data structures (such as lists, dicts, and tuples) with numerical leaf values β designed to simplify working with complex, hierarchically organized data. While such structures are often cumbersome to manipulate, PyTrees make them more manageable by allowing them to be flattened into a list of leaves along with a reusable structure blueprint in a _generic_ way. This enables flexible, generic operations like mapping and reducing from functional programming. By bringing those functional paradigms to structured data, PyTrees let you focus on what transformations to apply, not how to traverse the structure β no matter how deeply nested or complex it is.
There are so many quotable bits in this article, but I'll only go for
> We shouldn't have to be telling developers "oh just run it all in Docker". We should have designed this to be fundamentally secure from the get-go.
We really need to create security-by-default AI-tools where tech debt is actually managed, not added to at an exponential rate.
> economy runs on money, not GitHub stars
That's why we need sustainable open source.
(from https://xeiaso.net/blog/2025/avoiding-becoming-peg-dependency/)