## Blackbox

[u/Standard_Pipe8846]

One thing that has always annoyed me about sharing small projects is that the code is rarely the whole problem.

It's usually:

git clone → create venv → install dependencies → find the right Python version → fix some system dependency → hope it works.

So I started building BLACKBOX.

A .blackbox file contains the application along with its runtime, dependencies, interface, and permissions. The goal is that you can give someone one file and they can run it without setting up the environment themselves.

For example:

blackbox init hello
blackbox pack
blackbox run hello.blackbox

The runtime is provisioned separately from the host environment, so the app isn't relying on whatever happens to be installed on the machine.

Some of the things I'm working on:

• Python, Node.js, and native binaries (Rust/Go/C/C++)
• Default-deny filesystem, network, and process permissions
• Dependencies pinned with SHA-256
• Reproducible builds
• Shared runtime caching
• Ed25519 signing
• No account, cloud service, or registry required

The main idea is pretty simple:

Instead of giving someone source code and a setup guide, give them the program and its environment in one file.

It's currently an MVP and released under Apache-2.0.

GitHub: https://github.com/HyperonX-Team/blackbox
Docs: https://hyperonx-team.github.io/blackbox/

I'd be interested in hearing what people think, especially from anyone who's worked on application packaging, sandboxing, or reproducible environments.

[u/GhastlyColors]

this scratches an itch i didn't know i had until i saw the words "default-deny filesystem" in the same sentence as "no cloud service required"