smashini

Have been building this for the past two years.

It does analysis at scale: Searching for court filings, regulatory actions and investigative reporting. Then scoring companies across 11 ethical dimensions.

Built it because this kind of data and research isn't readily available and is important for giving companies accountability for how they operate :)

Any questions welcome!

Part of the cons is offset, if the single maintainer dissapears, nothing a fork can't fix :)

Yes, but they operate at the OS boundary, but we are defining application/business logic

OS controls answer "can this process make network requests?"

App-level policies answer "is this request, with these parameters, acceptable?"

Completely agree, though the LLM part of the scanner can help with that contextual part of the analysis.

Runtime enforcement already exists (the embedded governor wraps tool calls in-process); extending it with a quarantined contextual evaluator like you describe would the logical next step.

Thanks for the feedback, actually will raise an issue on that to explore

The scanner is just one part of the codebase, good for maintaining quality in a pipeline.

There is also @makerchecker/embedded, which has runtime permission primitives you wrap around the agent's actions, so the restraints live in the app exactly like you're describing

Less whack-a-mole, more wrap the risky calls and they're bound

So Linux can prevent an agent from opening /etc/passwd.

Linux cannot stop an agent from calling:

POST /wire-transfer amount=5,000,000

should be fixed and released now :)

I’d say the biggest difference would be: 1. Parameter-aware rules: OS permissions don’t know your application logic. (How would you tell OS permissions not to let your AI to trade on over 1M dollars) 2. You can’t easily model multi-pary and RBAC. 3. Agents call remote APIs for alot of those tools. Native OS doesn’t really parse web traffic to decide if a request is safe or not. OS sandboxing is good for host security, but not necessarily for governing business logic or AI agents

oopsie doopsie, release pipeline failed fixing now...

Honestly, amazing stuff. For all the flak that the EU gets this is absolutely an essential regulation

Hey all :)

I've been working an open-source toolkit to stop AI agents from running amok.

You can scan your code (Python, JS, TS) and it will flag any risks and can offer fixes. It runs offline, but you can wire an LLM to do code analysis as well.

You can run it with:

npx @makerchecker/scan

Would love to get any feedback!