Vulnerability Database · Go · Package report
github.com/tailscale/depaware: vulnerability history, versions and safety
github.com/tailscale/depaware 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/tailscale/depaware v0.0.0-20260720165112-f20f66241ec6 i
Updated on 23 Oct 2026
Good news: v0.0.0-20260720165112-f20f66241ec6, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Inactive
What to do: Stay on v0.0.0-20260720165112-f20f66241ec6 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20260720165112-f20f66241ec6 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20260720165112-f20f66241ec6 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 458 i
- OpenSSF scorecard 2/10 i
- Last release 3 months ago i
- Licence BSD-3-Clause 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/tailscale/depaware, 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-20260720165112-f20f66241ec6 20 Jul 2026
- v0.0.0-20260426051615-835d31c2ca68 26 Apr 2026
- v0.0.0-20260411190121-d5eabbd4636d 11 Apr 2026
- v0.0.0-20251001183927-9c2ad255ef3f 01 Oct 2025
- v0.0.0-20250112153213-b748de04d81b 12 Jan 2025
- v0.0.0-20250111143749-866af28b7c79 11 Jan 2025
- v0.0.0-20241028160002-3d7f3b30ed0e 28 Oct 2024
- v0.0.0-20240804103531-585336c3e1b3 04 Aug 2024
- v0.0.0-20210812192245-93f5ed019a89 12 Aug 2021
- v0.0.0-20210622194025-720c4b409502 22 Jun 2021
- v0.0.0-20201214215404-77d1e9757027 14 Dec 2020
- v0.0.0-20201210233412-71b54857b5d9 10 Dec 2020
- v0.0.0-20201210231258-91a2c3f1d1e9 10 Dec 2020
- v0.0.0-20201102210757-e2f543bafb1d 02 Nov 2020
- v0.0.0-20201003033024-5d95aab075be 03 Oct 2020
- v0.0.0-20201002180857-4fbc64c5c030 02 Oct 2020
- v0.0.0-20200914232109-e09ee10c1824 14 Sep 2020
- v0.0.0-20200914201916-3f1070fd0d55 14 Sep 2020
- v0.0.0-20200910145248-cb751026f10d 10 Sep 2020
- v0.0.0-20200909191943-cb50ac86be44 09 Sep 2020
- v0.0.0-20200909185729-8ca448326e3a 09 Sep 2020
All 21 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/tailscale/depaware
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/tailscale/depaware
Is github.com/tailscale/depaware safe to use?
Vulert has no vulnerabilities on record for github.com/tailscale/depaware 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/tailscale/depaware's Vulert package health score?
Vulert scores github.com/tailscale/depaware 70/100, which reads as in good shape. 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/tailscale/depaware affected?
No. v0.0.0-20260720165112-f20f66241ec6, 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/tailscale/depaware should I use?
v0.0.0-20260720165112-f20f66241ec6 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/tailscale/depaware have?
0 vulnerabilities are recorded for github.com/tailscale/depaware 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/tailscale/depaware vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/tailscale/depaware 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/tailscale/depaware 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/tailscale/depaware for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/tailscale/depaware version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.