Skip to main content

A completely randomized order of secrets, with security in mind.

Project description


alt text A completely randomized order of secrets; built with security in mind. Secrets can be automatically generated on a time interval or manually generated. Polysecrets keeps the guessing away from the human in exchange for a truly secret, randomized signing order. Instead of a hardcoded secret that can be stolen during a security breach, Polysecrets, randomizes the provided string in a way that a secret produced at 8:00pm can be completely different from a secret produced at 8:01pm, on the same server.

Libraries - v0.1.4

NodeJS: Python:


Let's connect on LinkedIn:


  • Python 3.5+
  • Windows, OSX or Linux



git clone
cd polysecrets

python -m pip install --upgrade .
pip install --upgrade .

PyPi (Pip)

python -m pip install --upgrade polysecrets
pip install --upgrade polysecrets

How To Use

Polysecrets can be used manually or automated. Automated use can be provided a time (in seconds) for how often a new secret should be generated, the default time is set to 30 seconds. You do not have to provide a secret to Polysecrets class, but you can if you'd like certain characters in your secret. Reminder, the secret is a collection of randomly ordered characters so the secret you provide will not be used entirely.

** Look through examples folder **

Automated (this will add the secret to your environment)

from os import environ
from polysecrets import PolySecrets

config = dict(
        secret='rAnd0m_s3cr3t',  # or use default
        length=10,  # default
        interval=30,  # default (only if you're using automated)
        uuid='yes',  # default
        mixcase=False,  # default
        persist=False,  # default

automated = PolySecrets(config).automated()  # default time is set to 30 seconds
print(environ['secret'])  # confirm secret is available
automated.terminate()  # stop automation


from polysecrets import PolySecrets

config = dict(
        secret='rAnd0m_s3cr3t',  # or use default
        length=10,  # default
        interval=30,  # default (only if you're using automated)
        uuid='yes',  # default
        mixcase=False,  # default
        persist=False,  # default

secret = PolySecrets(config).manual()
print(secret)  # confirm secret is available

Refer to examples folder for all use cases. Also refer to 'Notes' section at the bottom of this README.
If you want your environment variables cleared after Polysecrets terminates, do the following:

from polysecrets import PolySecrets
from os import environ

config = {}  # use all defaults
automated = PolySecrets(config=config, clear_on_exit=True).automated()
automated.terminate()  # forcibly remove envs


You can you use the persistence feature to keeps record of the secrets produced, and verifies that no secret has been duplicated. You will need to have a .env file with the MongoDB credentials inside. An example of the .env file is below:


# Host URI Example


  • All variables with the '#' prefix are optional; defaults will be assigned.
  • Host variable can also be a full MongoDB URI. If so, it will ignore all other variables.


You can do the following with Polysecrets:

  • Manually or Automatically generate new secrets
  • Change time interval for new secret generation (for Automated feature)
  • Change the length of the final Polysecrets secret (refer to Notes at end of README)
  • Choose whether to generate secrets with just UUIDs, Alphanumeric characters or both
  • Persist generated secrets to ensure the same secret isn't used twice

The CLI (below) has full details of each option (except automated option)


You can use Polysecrets as a command line tool. CLI does not provided automated feature. If secret is left out, it will default to a random string built into the Polysecrets. An example is below:

polysecrets --length 20 go 

Help menu

Usage: polysecrets [OPTIONS] GO

  -s, --secret TEXT       The secret string
  -l, --length INTEGER    Length of the secret. Secret has a minimum length of
  -i, --interval INTEGER  How frequently should a new secret be generated (in
  -u, --uuid TEXT         Whether to use UUIDs or Alphanumeric characters for
                          secret generation - yes, no, both
  -m, --mixcase BOOLEAN   Decide whether or not to mix the case of
                          alphacharacters in secret string
  -p, --persist DICT      Never get the same secret twice with persistence
                          from MongoDB
  --symbols BOOLEAN       Whether or not to use special characters in secret.
                          This will only increase the probability of appending
                          a special character.
  --version               Show the version and exit.
  --help                  Show this message and exit.


  • JSON Web Tokens
  • Certificate Signing
  • Hashing
  • Various scenarios of Cryptography

What's Next

(refer to Changelog)

If you have found a bug or would like to create new features, make a PR!


v0.1.4 - June 1st, 2021

  • Improved CLI tool
  • Fixed persistence bug
  • Simplified defaults

v0.1.3 - July 11th, 2019

  • Improved code and squashed bugs

v0.1.2 - July 1st, 2019

  • Persistence added. You can now avoid duplicate secrets being generated.
  • Node version is now available. Install:
npm install polysecrets
  • Improved code and squashed bugs

v0.1.1 - June 4th, 2019

  • Custom secret string length, with a minimum of 10 characters
  • You may mix the secret, in combination with the provided secret string, with UUIDs, alphanumeric characters or both.
  • You can now select between upper and lower case mixing during secret generation

v0.1.0 - June 3rd, 2019

  • Manually and autogenerated secrets, with fixed secret length
  • Polysecrets CLI added


  • If you change the length of the secret via the 'length' parameter, you will notice that the secret string you provided will not contain all the characters provided. If you want the final secret to contain all the exact same characters, then provide the exact string length to Polysecrets 'length' field.

  • The secret provided in the config is just used as reference characters and are not guaranteed to be a part of the final secret. If you would like to use the secret you provide I would recommend going the traditional route; add secret to your project .env file and use Able's Py.Envs python library.

  • You cannot run manual and automated in the same file. You will throw an error.

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

polysecrets-0.1.4.tar.gz (7.5 kB view hashes)

Uploaded source

Built Distribution

polysecrets-0.1.4-py3-none-any.whl (8.2 kB view hashes)

Uploaded py3

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page