Vulnerability Database · Go · Package report
github.com/temoto/robotstxt: vulnerability history, versions and safety
github.com/temoto/robotstxt 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/temoto/robotstxt v1.1.2 i
Updated on 23 Oct 2026
Good news: v1.1.2, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Niche
- Community Quiet
What to do: Stay on v1.1.2 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.1.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.1.2 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 288 i
- OpenSSF scorecard 3/10 i
- Last release 66 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/temoto/robotstxt, 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.
- v1.1.3-0.20260525085122-cadd395bcc35 25 May 2026
- v1.1.3-0.20260217105422-863febf14c0e 17 Feb 2026
- v1.1.3-0.20251021144802-a517cd16902d 21 Oct 2025
- v0.0.0-20221109095134-1fe1f4f9bc7b 09 Nov 2022
- v1.1.3-0.20221109095134-1fe1f4f9bc7b 09 Nov 2022
- v1.1.3-0.20220908104222-be546eccf93d 08 Sep 2022
- v1.1.3-0.20220411224903-a68aeca94fff 11 Apr 2022
- v1.1.3-0.20220411222246-6b2d4c0a6ecd 11 Apr 2022
- v1.1.2 31 Mar 2021
- v1.1.2-0.20210303151152-0b2f4c43b7ed 03 Mar 2021
- v1.1.2-0.20200722125343-87d22cd7529c 22 Jul 2020
- v0.0.0-20191126171515-7c448aca1487 26 Nov 2019
- v1.1.2-0.20191126171515-7c448aca1487 26 Nov 2019
- v1.1.2-0.20191005102113-0c9d816f3895 05 Oct 2019
- v0.0.0-20190730135514-072b6a3a11ed 30 Jul 2019
- v1.1.2-0.20190730135514-072b6a3a11ed 30 Jul 2019
- v1.1.2-0.20190730135500-2b21ac5f4fcb 30 Jul 2019
- v0.0.0-20190703213251-3f668f68d41c 03 Jul 2019
- v1.1.1 03 Jul 2019
- v1.1.0 03 Jul 2019
- v0.0.0-20190703110036-3a27da55453b 03 Jul 2019
- v0.0.0-20190703084111-155d088cef12 03 Jul 2019
- v0.0.0-20180810133444-97ee4a9ee6ea 10 Aug 2018
- v0.0.0-20170603013557-9e4646fa7053 03 Jun 2017
- v0.0.0-20170109200312-5f8637625d10 09 Jan 2017
- v0.0.0-20170103224350-d53b7923f436 03 Jan 2017
- v0.0.0-20170101182027-217bb330e657 01 Jan 2017
- v0.0.0-20160601080807-99f6b48954d8 01 Jun 2016
- v0.0.0-20150626090821-b8a039be43ce 26 Jun 2015
- v0.0.0-20150114134638-c51489e759bc 14 Jan 2015
- v0.0.0-20140914080812-2f1297117982 14 Sep 2014
- v0.0.0-20140719185543-9344864c380c 19 Jul 2014
- v0.0.0-20140718203049-3098843c8d1c 18 Jul 2014
- v0.0.0-20121126154713-207003cc18bd 26 Nov 2012
- v0.0.0-20121004095053-164bac4d1e72 04 Oct 2012
- v0.0.0-20121003000951-08fdba6d242b 03 Oct 2012
- v0.0.0-20121003000951-0e01e6e0d24c 03 Oct 2012
- v0.0.0-20121003000951-64ca140e7cad 03 Oct 2012
- v0.0.0-20110531184931-7ceedec0c69d 31 May 2011
- v0.0.0-20110112150620-112c08bce46e 12 Jan 2011
- v0.0.0-20101228172605-76e575a54467 28 Dec 2010
- v0.0.0-20100825141719-ba302b8b9166 25 Aug 2010
- v0.0.0-20100824144710-3b10e011488e 24 Aug 2010
All 43 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.
03 Vulnerabilities
Recorded vulnerabilities for github.com/temoto/robotstxt
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/temoto/robotstxt
Is github.com/temoto/robotstxt safe to use?
Vulert has no vulnerabilities on record for github.com/temoto/robotstxt 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/temoto/robotstxt's Vulert package health score?
Vulert scores github.com/temoto/robotstxt 52/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 github.com/temoto/robotstxt affected?
No. v1.1.2, 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/temoto/robotstxt should I use?
v1.1.2 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/temoto/robotstxt have?
0 vulnerabilities are recorded for github.com/temoto/robotstxt 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/temoto/robotstxt vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/temoto/robotstxt 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/temoto/robotstxt 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/temoto/robotstxt for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/temoto/robotstxt version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.