Internal package mirrors

Organizations that restrict which package indexes machines are allowed to reach do not need anything special to install tCode beyond a normal PyPI mirror. It is a standard Python package, with no private registry, custom index, or vendor-specific build step of its own.

The same pip install tcode-cli command that works against the public index works identically against an internal mirror, as long as that mirror actually carries the package and pip is configured to look there in the usual way, through a pip config file or an --index-url flag.

This also means there is nothing tCode-specific to request from an internal packaging or security team beyond confirming the package is allowed and mirrored, the same review any other small, dependency-light Python package would go through.

If your mirror only carries an allow-listed subset of PyPI, the specific packages that need to be present are tCode itself plus its three runtime dependencies covered in Dependencies, nothing beyond that short list.

Air-gapped environments with no index access at all are the one genuine exception: without any reachable PyPI mirror, pip install cannot resolve or download anything, tCode included, and installation would need to happen through whatever offline package-transfer process your organization already uses for other Python packages.