PyPassKit is a Python package which generates secure and customisable passwords and passphrases, with zero dependencies.
This policy is effective from 16 July 2026. For more information, please read 01 - Updates.
Before using the library in your project, please read the security policy carefully.
| V | Date | Changes |
|---|---|---|
| v1.0 | 28 June 2026 | Added the date effective and section 01. |
| v1.1 | 16 July 2026 | Updated introduction, added sections 05 and 06. |
You will be notified of updates to this policy through the project website by clicking the 'Notifications' button.
Warning
If you've noticed a critical flaw with the package, do not open a public issue. Creating public issues about vulnerabilities gives malicious actors a heads-up before a patch can be rolled out.
Navigate to the Security tab of this repository, click Vulnerabilities under "Reporting", and click Report a vulnerability.
To help us fix the issue quickly, please include:
- A brief description of the vulnerability and its potential impact.
- Clear, step by step instructions or a minimal reproducible example to recreate the issue.
- The specific versions of the software affected.
Before reporting a vulnerability, please ensure that you are running the latest release of PyPassKit.
Warning
It is your responsibility to keep PyPassKit up to date.
Legacy releases will not be supported and will not receive backported patches.
This library is licensed under the MIT license, and is provided "AS IS", WITHOUT WARRANTY OF ANY KIND.
While I do my best to maintain the security and integrity of this library, you use the library at your own risk. I am not liable for data loss, damages or security breaches resulting from its use.
PyPassKit is distributed without any third-party dependencies and will never use external dependencies. This is because security is paramount as opposed to adding more complex features that require additional packages.
This reduces the impact of supply-chain vulnerabilities. Supply chain attacks could compromise the integrity of the project and this has been mitigated by using zero third party dependencies.
By using this library, you accept responsibility for staying up-to-date to reduce the risk of security vulnerabilities. Furthermore, you are aware of how to report a critical security issue if you ever need to.