drak-ops — name reservation

This is not a functional package. It exists only to hold the PyPI name drak-ops so that nobody else can register it.

The real drak-ops is a private package belonging to Drak Marketing. It is never installed from PyPI — always by direct URL:

drak-ops[google] @ git+https://github.com/mharnett/drak-ops.git

Why this exists

A private package name that is not claimed on the public index is a dependency-confusion vector. If anyone ever writes pip install drak-ops without the URL — in a Dockerfile, a CI step, a README, or by hand — pip resolves it against PyPI and installs whatever is published there. Registering the name ourselves means that path leads to this inert placeholder instead of to a stranger's code.

The name became publicly discoverable through an open-source MCP package that referenced it, which is what prompted the reservation.

What it deliberately does not do

It ships a module named drak_ops_placeholder, not drak_ops. A placeholder that provided a real-looking drak_ops package would shadow the private one if both ever landed in the same environment — turning a defensive measure into the outage it was meant to prevent. Importing anything from it raises with the correct install line.

Maintaining it

Nothing to do. It never needs a new release. If it somehow must be rebuilt:

python3 -m venv /tmp/venv && /tmp/venv/bin/pip install -q build twine
/tmp/venv/bin/python -m build
/tmp/venv/bin/twine check dist/*
/tmp/venv/bin/twine upload dist/*

Note drak-ops, drak_ops and Drak.Ops all normalise to the same PyPI project (PEP 503), so this single registration covers them. drakops — no separator — is a different name and is not covered.