Vulnerability Database · PyPI · Package report
tgcrypto: vulnerability history, versions and safety
tgcrypto is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the PyPI ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on tgcrypto 1.2.5 i
Updated on 23 Oct 2026
Good news: 1.2.5, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Niche
- Community Quiet
What to do: Stay on 1.2.5 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.2.5 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 1.2.5 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 155 packages i
- Stars 211 i
- OpenSSF scorecard 2/10 i
- Last release 47 months ago i
- Licence non-standard i
Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Versions
Which versions are affected
Every version Vulert tracks for tgcrypto, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.
- 1.2.5 11 Nov 2022
- 1.2.4 11 Oct 2022
- 1.2.3 08 Jan 2022
- 1.2.2 23 Oct 2020
- 1.2.1 30 Apr 2020
- 1.2.0 27 Nov 2019
- 1.1.1 19 Sep 2018
- 1.0.4 26 Mar 2018
- 1.0.3 13 Mar 2018
- 1.0.2 19 Feb 2018
- 1.0.1 19 Feb 2018
- 1.0.0 17 Feb 2018
- 0.0.1b1 27 Jan 2018
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 1.2.5 | 11 Nov 2022 | none | non-standard | — | Details → |
| 1.2.4 | 11 Oct 2022 | none | non-standard | — | Details → |
| 1.2.3 | 08 Jan 2022 | none | non-standard | — | Details → |
| 1.2.2 | 23 Oct 2020 | none | non-standard | — | Details → |
| 1.2.1 | 30 Apr 2020 | none | non-standard | — | Details → |
| 1.2.0 | 27 Nov 2019 | none | non-standard | — | Details → |
| 1.1.1 | 19 Sep 2018 | none | non-standard | — | Details → |
| 1.0.4 | 26 Mar 2018 | none | non-standard | — | Details → |
| 1.0.3 | 13 Mar 2018 | none | non-standard | — | Details → |
| 1.0.2 | 19 Feb 2018 | none | non-standard | — | Details → |
| 1.0.1 | 19 Feb 2018 | none | non-standard | — | Details → |
| 1.0.0 | 17 Feb 2018 | none | non-standard | — | Details → |
| 0.0.1b1 | 27 Jan 2018 | none | non-standard | — | Details → |
All 13 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for tgcrypto
No vulnerabilities match this view.
Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback
Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315
Questions
About tgcrypto
Is tgcrypto safe to use?
Vulert has no vulnerabilities on record for tgcrypto in PyPI at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is tgcrypto's Vulert package health score?
Vulert scores tgcrypto 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).
Is the latest version of tgcrypto affected?
No. 1.2.5, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.
Which version of tgcrypto should I use?
1.2.5 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.
How many vulnerabilities does tgcrypto have?
0 vulnerabilities are recorded for tgcrypto in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.
How often are new tgcrypto vulnerabilities disclosed?
0 vulnerabilities were recorded for tgcrypto in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.
Which versions of tgcrypto are affected?
Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.
How do I monitor tgcrypto for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the tgcrypto version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.