Curate your own repository of Perl modules
Switch branches/tags
release-0.09999 release-0.09998 release-0.09996 release-0.09995 release-0.09993 release-0.09992_02 release-0.09992_01 release-0.09992 release-0.09991 release-0.0999 release-0.0998 release-0.0997 release-0.0996 release-0.0995 release-0.0994_04 release-0.0994_03 release-0.0994_02 release-0.0994_01 release-0.0994 release-0.0993 release-0.0992 release-0.0991 release-0.099 release-0.098_01 release-0.098 release-0.097_04 release-0.097_03 release-0.097_02 release-0.097_01 release-0.097 release-0.096 release-0.095 release-0.094 release-0.093 release-0.092 release-0.091 release-0.090 release-0.089 release-0.088 release-0.087_05 release-0.087_04 release-0.087_03 release-0.087_01 release-0.087 release-0.086 release-0.085 release-0.084_02 release-0.084_01 release-0.084 release-0.083 release-0.082 release-0.081 release-0.080 release-0.079_04 release-0.079_01 release-0.068 release-0.067 release-0.066 release-0.065_06 release-0.065_05 release-0.065_04 release-0.065_03 release-0.065_02 release-0.065_01 release-0.065 release-0.064 release-0.063 release-0.062 release-0.061 release-0.060 release-0.059 release-0.058 release-0.057 release-0.056 release-0.055 release-0.054 release-0.053 release-0.052 release-0.051 release-0.050 release-0.048 release-0.047 release-0.046 release-0.045 release-0.044 release-0.043 release-0.042 release-0.041 release-0.040_003 release-0.040_002 release-0.040_001 release-0.038 release-0.037 release-0.036 release-0.035 release-0.033 release-0.032 release-0.031 release-0.030 release-0.029
Nothing to show
Clone or download
thaljef Merge pull request #241 from mschout/term-readkey-workaround
Add workaround for Term::ReadKey >= 2.37
Latest commit 866afde May 2, 2018
Failed to load latest commit information.
lib Fix indexing of modules that declare a provides file of META.{json,yml} May 1, 2018
t Fix indexing of modules that declare a provides file of META.{json,yml} May 1, 2018
xt Removes workarounds, now that Module::Metadata is fixed. Jul 17, 2016
.gitignore Tell git to ignore tidyall stuff. Jul 8, 2013
.mailmap Add Kahlil to the mail map so he only appears once in the contributor… Mar 24, 2015
.tidyallrc Adding tidyall config. Jul 8, 2013
Changes Fix indexing of modules that declare a provides file of META.{json,yml} May 1, 2018
MANIFEST.SKIP Exclude tidyall cache dir from dist. Jul 9, 2013 Fix indexing of modules that declare a provides file of META.{json,yml} May 1, 2018
dist.ini Bump VERSION. Aug 6, 2017
weaver.ini Trying to sort out encoding problems. Jan 7, 2014


Pinto - Curate a repository of Perl modules


version 0.14


See pinto to create and manage a Pinto repository.

See pintod to allow remote access to your Pinto repository.

See Pinto::Manual for more information about the Pinto tools.

Stratopan for hosting your Pinto repository in the cloud.


Pinto is an application for creating and managing a custom CPAN-like repository of Perl modules. The purpose of such a repository is to provide a stable, curated stack of dependencies from which you can reliably build, test, and deploy your application using the standard Perl tool chain. Pinto supports various operations for gathering and managing distribution dependencies within the repository, so that you can control precisely which dependencies go into your application.


Pinto is inspired by Carton, CPAN::Mini::Inject, and MyCPAN::App::DPAN, but adds a few interesting features:

  • Pinto supports multiple indexes

    A Pinto repository can have multiple indexes. Each index corresponds to a "stack" of dependencies that you can control. So you can have one stack for development, one for production, one for feature-xyz, and so on. You can also branch and merge stacks to experiment with new dependencies or upgrades.

  • Pinto helps manage incompatibles between dependencies

    Sometimes, you discover that a new version of a dependency is incompatible with your application. Pinto allows you to "pin" a dependency to a stack, which prevents it from being accidentally upgraded (either directly or via some other dependency).

  • Pinto has built-in version control

    When things go wrong, you can roll back any of the indexes in your Pinto repository to a prior revision. Also, you can view the complete history of index changes as you add or upgrade dependencies.

  • Pinto can pull archives from multiple remote repositories

    Pinto can pull dependencies from multiple sources, so you can create private (or public) networks of repositories that enable separate teams or individuals to collaborate and share Perl modules.

  • Pinto supports team development

    Pinto is suitable for small to medium-sized development teams and supports concurrent users. Pinto also has a web service interface (via pintod), so remote developers can use a centrally hosted repository.

  • Pinto has a robust command line interface.

    The pinto utility has commands and options to control every aspect of your Pinto repository. They are well documented and behave in the customary UNIX fashion.

  • Pinto can be extended.

    You can extend Pinto by creating Pinto::Action subclasses to perform new operations on your repository, such as extracting documentation from a distribution, or grepping the source code of several distributions.

Pinto vs PAUSE

In some ways, Pinto is similar to PAUSE. Both are capable of accepting distributions and constructing a directory structure and index that Perl installers understand. But there are some important differences:

  • Pinto does not promise to index exactly like PAUSE does

    Over the years, PAUSE has evolved complicated heuristics for dealing with all the different ways that Perl code is written and packaged. Pinto is much less sophisticated, and only aspires to produce an index that is "good enough" for most situations.

  • Pinto does not understand author permissions

    PAUSE has a system of assigning ownership and co-maintenance permission of modules to specific people. Pinto does not have any such permission system. All activity is logged so you can identify the culprit, but Pinto expects you to be accountable for your actions.

  • Pinto does not enforce security

    PAUSE requires authors to authenticate themselves before they can upload or remove modules. Pinto does not require authentication, so any user with sufficient file permission can potentially change the repository. However pintod does support HTTP authentication, which gives you some control over access to a remote repository.


For now, the Pinto API is private and subject to radical change without notice. Any API documentation you see is purely for my own references. In the meantime, the command line utilities mentioned in the "SYNOPSIS" are your public user interface.



You can find documentation for this module with the perldoc command.

perldoc Pinto


The following websites have more information about this module, and may be of help to you. As always, in addition to those websites please use your favorite search engine to discover more resources.

Internet Relay Chat

You can get live help by using IRC ( Internet Relay Chat ). If you don't know what IRC is, please read this excellent guide: Please be courteous and patient when talking to us, as we might be busy or sleeping! You can join those networks/channels and get help:


    You can connect to the server at '' and join this channel: #pinto then talk to this person for help: thaljef.

Bugs / Feature Requests

Source Code

The code is open to the world, and available for you to hack on. Please feel free to browse it and play with it, or whatever. If you want to contribute patches, please send me a diff or prod me to pull from your repository :)

git clone git://



Jeffrey Ryan Thalhammer


This software is copyright (c) 2015 by Jeffrey Ryan Thalhammer.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.