Dependably Packages · Hex

A private Hex repository for Mix and Rebar3

One repository for Mix and Rebar3, signed with your organization's key. hex.pm packages come through a pull-through cache that verifies every checksum; your own packages publish with a token; the policy gate decides what reaches a build.

mix · rebar3

Point Hex at your registry

Fetch the public key, register the repository, then name it on each dependency that should resolve through it. The Setup page in the web UI shows this with your key filled in.

The placeholders are your base URL and a token from the web UI. The guide covers the same steps for a single project, plain HTTP, verifying the change, and reverting it.

bash · repo.example.com
curl -sSf https://repo.example.com/hex/public_key -o dependably-hex.pem
mix hex.repo add dependably https://repo.example.com/hex \
  --public-key dependably-hex.pem --auth-key <your token>

What happens to every fetch

The client sees a registry. Behind it, Dependably Packages stages each upstream artefact and refuses the ones that fail a check you configured.

  • The checksum is verified against the digest the upstream publishes before the artefact is stored.
  • The version is screened against OSV, and the policy gate can refuse on licence, severity, CISA KEV, EPSS, install scripts, or release age.
  • A name your organization reserves cannot be squatted upstream and resolved into your builds.
  • Every refusal is written to the audit log with the arm that refused it, so a 403 in CI is explained in the web UI.

Verify, publish, revert

The Hex guide continues with a verification step, publishing your own packages, and reverting the configuration if you need to.