skip to navigation
skip to content

peep 1.0.2

A "pip install" that is cryptographically guaranteed repeatable

Latest Version: 3.1.2

Historically, deploying Python projects has been a pain in the neck for the security-conscious. First, PyPI lets authors change the contents of their packages without revving their version numbers. Second, any future compromise of PyPI or its caching CDN means you could get a package that’s different from the one you signed up for. If you wanted to guarantee known-good dependencies for your deployment, you had to either run a local PyPI mirror–manually uploading packages as you vetted them–or else check everything into a vendor library, necessitating a lot of fooling around with your VCS (or maintaining custom tooling) to do upgrades.

Peep fixes much of that.

Vet your packages, put hashes of the PyPI-sourced tarballs into requirements.txt, use peep install instead of pip install, and let the crypto do the rest. If a downloaded package doesn’t match the hash, peep will freak out, and installation will go no further. No servers to maintain, no enormous vendor libs to wrestle. Just requirements.txt with some funny-looking comments and peace of mind.

Quick FAQ

  1. Peep guarantees repeatability.

    If you peep install package x version y, every subsequent install of package x version y will be the same as the original, or Peep will complain.

  2. Peep does not vet your packages.

    Peep is not a substitute for vetting your packages. If you don’t vet them, then they are not vetted.

  3. Peep does not alleviate trust problems with authors or package indexes.

    All peep does is guarantee that subsequent downloads of package x version y are the same as the first one you did. It doesn’t guarantee the author of that package is trustworthy. It doesn’t guarantee that the author of that package released that package. It doesn’t guarantee that the package index is trustworthy.

Switching to Peep

  1. Install peep:

    pip install peep
  2. Use peep to install your project once:

    cd yourproject
    peep install -r requirements.txt

    You’ll get output like this:

    <a bunch of pip output>
    The following packages had no hashes specified in the requirements file,
    which leaves them open to tampering. Vet these packages to your
    satisfaction, then add these "sha256" lines like so:
    # sha256: L9XU_-gfdi3So-WEctaQoNu6N2Z3ZQYAOu4-16qor-8
    # sha256: YhddA1kUpMLVODNbhIgHfQn88vioPHLwayTyqwOJEgY
    # sha256: qF4YU3XbdcEJ-Z7N49VUFfA15waKgiUs9PFsZnrDj0k
    # sha256: u_8C3DCeUoRt2WPSlIOnKV_MAhYkc40zNZxDlxCA-as
    Not proceeding to installation.
  3. Vet the packages coming off PyPI in whatever way you typically do.

  4. Add the recommended hash lines to your requirements.txt, each one directly above the requirement it applies to. (The hashes are of the original, compressed tarballs from PyPI.)

  5. In the future, always use peep install to install your requirements. You are now cryptographically safe!

The Fearsome Warning

If, during installation, a hash doesn’t match, peep will say something like this:

REQUIREMENTS FILE. If you have updated the package versions, update the
hashes. If not, freak out, because someone has tampered with the packages.

    requests: expected FWvz7Ce6nsfgz4--AoCHGAmdIY3kA-tkpxTXO6GimrE
                   got YhddA1kUpMLVODNbhIgHfQn88vioPHLwayTyqwOJEgY

It will then exit with a status of 1. Freak out appropriately.

Other Niceties

  • peep implicitly turns on pip’s --no-deps option so unverified dependencies of your requirements can’t sneak through.

  • All non-install commands just fall through to pip, so you can use peep all the time if you want. This comes in handy for existing scripts that have a big $PIP=/path/to/pip at the top.

  • peep-compatible requirements files remain entirely usable with pip, because the hashes are just comments, after all.

  • Have a manually downloaded package you’ve vetted? Run peep hash on its tarball (the original, from PyPI–be sure to keep it around) to get its hash line:

    % peep hash nose-1.3.0.tar.gz
    # sha256: TmPMMyXedc-Y_61AvnL6aXU96CRpUXMXj3TANP5PUmA
  • If a package is already present–which might be the case if you’re installing into a non-empty virtualenv–peep doesn’t bother downloading or building it again. It assumes you installed it with peep in a previous invocation and thus trusts it. Re-using a virtualenv during deployment can really speed things up, but it does leave open the question of how to remove dependencies which are no longer needed.


Peep was designed for unsupervised continuous deployment scenarios. In such scenarios, manual ahead-of-time prepartion on the deployment machine is a liability: one more thing to go wrong. To relieve you of having to install (and upgrade) peep by hand on your server or build box, we’ve made peep embeddable. You can copy the file directly into your project’s source tree and call it from there in your deployment script. This also gives you an obvious starting point for your chain of trust: however you trust your source code is how you trust your copy of peep, and peep verifies everything else via hashes. (Equivalent would be if your OS provided peep as a package–presumably you trust your OS packages already–but this is not yet common.)


Are you suddenly getting the Fearsome Warning? Maybe you’re really in trouble, but maybe something more innocuous is happening.

Architecture-Specific Packages

If your packages install from wheels or other potentially architecture-specific sources, their hashes will obviously differ across platforms. If you deploy on more than one, you’ll need more than one hash.

Old PyPI Roulette

A few packages offer downloads in multiple formats: for example, zips and tarballs. PyPI used to be unpredictable as to which it offered first, and pip simply takes the first one offered. Thus, if you’re running an old version of PyPI internally or have some other Cheeseshop implementation which lacks a stable sort order, some packages may effectively have more than one valid hash for a given version.

How To Specify Multiple Hashes

To support these scenarios, you can stack up multiple known-good hashes above a requirement, as long as they are within a contiguous block of commented lines:

# Tarball:
# sha256: lvpN706AIAvoJ8P1EUfdez-ohzuSB-MyXUe6Rb8ppcE
# And the zip file:
# sha256: 6QTt-5DahBKcBiUs06BfkLTuvBu1uF7pblb_bPaUONU

If you don’t want to wait until you’re bitten by this surprise, use the peep hash command to find hashes of each equivalent archive for a package. I like to vet one of them (say, the tarball), then download the other and use a file comparison tool to verify that they have identical contents. Then I run peep hash over both original archives, like so, and add the result to my requirements.txt:

% peep hash mock-0.8.0.tar.gz
# sha256: lvpN706AIAvoJ8P1EUfdez-ohzuSB-MyXUe6Rb8ppcE
# sha256: 6QTt-5DahBKcBiUs06BfkLTuvBu1uF7pblb_bPaUONU

Version History

  • Add support for .tar.bz2 archives. (Paul McLanahan)
  • Fix error (which failed safe) installing packages whose distro names contain underscores. (Chris Ladd)
  • Add wheel support. Peep will now work fine when pip decides to download a wheel file. (Paul McLanahan)
  • Don’t crash when trying to report a missing hash on a package that’s already installed.
  • Put the operative parts of peep into a single module rather than a package, and make it directly executable. (Brian Warner)
  • Support installing into non-empty virtualenvs, for speed. We do this by trusting any already-installed package which satisfies a requirement. This means you no longer have to rebuild lxml, for instance, each time you deploy.
  • Wrap text output to 80 columns for nicer word wrap.

Make some practical tweaks for projects which bootstrap their trust chains by checking a tarball of peep into their source trees.

  • Start supporting versions of pip back to 0.6.2 (released in January 2010). This way, you can deploy trustworthily on old versions of RHEL just by checking a tarball of peep into your source tree and pip-installing it; you don’t have to check in pip itself or go to the bother of unpacking the peep tarball and running python install from your deploy script.
  • Remove the explicit dependency on pip. This is so a blithe call to pip install peep.tar.gz without --no-deps doesn’t go out and pull an untrusted package from PyPI. Instead, we scream at runtime if pip is absent or too old. Fail safe.
  • Add peep hash subcommand.
  • Require pip>=1.2, as lower versions have a bug that causes a crash on peep install.
  • Rework how peep downloads files and determines versions so we can tolerate PEP-386-noncompliant package version numbers. This amounted to a minor rewrite.
  • Remove indentation from hash output so you don’t have to dedent it after pasting it into requirements.txt.
  • Support Windows and other non-Unix OSes.
  • The hash output now includes the actual version numbers of packages, so you can just paste it straight into your requirements.txt.
  • Add a shebang line so you can actually run peep after doing pip install peep. Sorry, folks, I was doing develop on my own box.
  • Fix repeated-logging bug.
  • Fix spurious error message about not having any requirements files.
  • Pass pip’s exit code through to the outside for calls to non-install subcommands.
  • Improve spacing in the final output.
  • Proof of concept. Does all the crypto stuff. Should be secure. Some rough edges in the UI.
File Type Py Version Uploaded on Size
peep-1.0.2.tar.gz (md5) Source 2014-04-02 12KB