Vulnerability Database · Go · Package report
github.com/kr/pty: vulnerability history, versions and safety
github.com/kr/pty is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/kr/pty v1.1.8 i
Updated on 23 Oct 2026
Good news: v1.1.8, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Little adoption
- Community Inactive
What to do: Stay on v1.1.8 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.1.8 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.1.8 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 23 i
- OpenSSF scorecard 1/10 i
- Last release 87 months ago i
- Licence MIT i
Version list, release dates, licence and dependants published by the Go module proxy, 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 github.com/kr/pty, 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.
- v0.0.0-20190702030844-24b51915630e 02 Jul 2019
- v1.1.7-0.20190702030844-24b51915630e 02 Jul 2019
- v1.1.8 02 Jul 2019
- v1.1.7 29 Jun 2019
- v1.1.6 29 Jun 2019
- v0.0.0-20190401031551-b6e1bdd4a4f8 01 Apr 2019
- v1.1.5 01 Apr 2019
- v1.1.5-0.20190401031551-b6e1bdd4a4f8 01 Apr 2019
- v0.0.0-20190318123844-521317be5ebc 18 Mar 2019
- v1.1.4 18 Mar 2019
- v0.0.0-20190131011033-7dc38fb350b1 31 Jan 2019
- v1.1.4-0.20190131011033-7dc38fb350b1 31 Jan 2019
- v1.1.4-0.20190131005902-38258927ffe4 31 Jan 2019
- v0.0.0-20180915150018-db8e3cd836b8 15 Sep 2018
- v1.1.3 15 Sep 2018
- v0.0.0-20180620151222-fa756f09eeb4 20 Jun 2018
- v1.1.2 20 Jun 2018
- v0.0.0-20180113180813-282ce0e5322c 13 Jan 2018
- v1.1.1 13 Jan 2018
- v1.1.1-0.20180113180753-f8811ff0e5ce 13 Jan 2018
- v0.0.0-20180106191130-1278f20d9cf7 06 Jan 2018
- v1.1.0 06 Jan 2018
- v0.0.0-20171006174801-95d05c1eef33 06 Oct 2017
- v1.0.1 06 Oct 2017
- v0.0.0-20170307145309-2c10821df3c3 07 Mar 2017
- v1.0.0 07 Mar 2017
- v0.0.0-20160716204620-ce7fa45920dc 16 Jul 2016
- v0.0.0-20160714130311-ed84cf86c907 14 Jul 2016
- v0.0.0-20160624121903-a6bad5ee6fc6 24 Jun 2016
- v0.0.0-20160520155922-0467868096db 20 May 2016
- v0.0.0-20160520132514-c0bea8ed3c8f 20 May 2016
- v0.0.0-20151104204415-fe7bf4339680 04 Nov 2015
- v0.0.0-20151007230424-f7ee69f31298 07 Oct 2015
- v0.0.0-20150511174710-5cf931ef8f76 11 May 2015
- v0.0.0-20150511082617-35af567f7332 11 May 2015
- v0.0.0-20141217211937-05017fcccf23 17 Dec 2014
- v0.0.0-20141204132103-9cf8a72e81a7 04 Dec 2014
- v0.0.0-20141203132500-e615e17b3e9e 03 Dec 2014
- v0.0.0-20141125103231-b1c5cc8377e0 25 Nov 2014
- v0.0.0-20141121105921-46d423f13f53 21 Nov 2014
- v0.0.0-20140316075115-67e2db24c831 16 Mar 2014
- v0.0.0-20140314152851-88e4fdb5b466 14 Mar 2014
- v0.0.0-20140305042229-98c7b800832d 05 Mar 2014
- v0.0.0-20140304052338-7a543c8bf642 04 Mar 2014
- v0.0.0-20140304051956-76284c52ce47 04 Mar 2014
- v0.0.0-20130926155747-3b1f6487b7fc 26 Sep 2013
- v0.0.0-20130317013008-27435c699bae 17 Mar 2013
- v0.0.0-20121204073444-c46bdbf4af2e 04 Dec 2012
- v0.0.0-20121204022106-02033fc6c559 04 Dec 2012
- v0.0.0-20121103231705-1fb082f5698c 03 Nov 2012
- v0.0.0-20120613122954-9e03abc5be12 13 Jun 2012
- v0.0.0-20120405210733-44e8fe6bc91a 05 Apr 2012
- v0.0.0-20120202054144-3b1c6581cb38 02 Feb 2012
- v0.0.0-20110524190843-227762de5212 24 May 2011
- v0.0.0-20110503212449-12319125d6d8 03 May 2011
All 55 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 github.com/kr/pty
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 github.com/kr/pty
Is github.com/kr/pty safe to use?
Vulert has no vulnerabilities on record for github.com/kr/pty in Go 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 github.com/kr/pty's Vulert package health score?
Vulert scores github.com/kr/pty 42/100, which reads as risky. 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 github.com/kr/pty affected?
No. v1.1.8, 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 github.com/kr/pty should I use?
v1.1.8 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 github.com/kr/pty have?
0 vulnerabilities are recorded for github.com/kr/pty in the Go 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 github.com/kr/pty vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/kr/pty 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 github.com/kr/pty 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 github.com/kr/pty for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/kr/pty version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.