Vulnerability Database · Go · Package report
github.com/grafana/dataplane/sdata: vulnerability history, versions and safety
github.com/grafana/dataplane/sdata 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/grafana/dataplane/sdata v0.0.9 i
Updated on 23 Oct 2026
Good news: v0.0.9, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Slowing
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.0.9 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.9 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.9 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 14 i
- Last release 30 months ago i
- Licence Apache-2.0 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/grafana/dataplane/sdata, 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.10-0.20250507104347-80610b456b95 07 May 2025
- v0.0.10-0.20250501144321-568ed02f069c 01 May 2025
- v0.0.10-0.20241125081959-a81ddd0d44ca 25 Nov 2024
- v0.0.10-0.20241015135217-29ca1e77b2c1 15 Oct 2024
- v0.0.10-0.20241011094127-a5cd19832543 11 Oct 2024
- v0.0.10-0.20240627125526-afa23908e3e3 27 Jun 2024
- v0.0.9 16 Apr 2024
- v0.0.9-0.20240415211207-3be10b446750 15 Apr 2024
- v0.0.8 15 Apr 2024
- v0.0.8-0.20240409212435-4bd1afeef43f 09 Apr 2024
- v0.0.8-0.20240216161101-9e5ff2e8c589 16 Feb 2024
- v0.0.7 16 Jan 2024
- v0.0.7-0.20240116175916-ec4a6f50fe7d 16 Jan 2024
- v0.0.7-0.20231106143248-c0f1d0ca6811 06 Nov 2023
- v0.0.7-0.20231025074516-dddcaf5eba15 25 Oct 2023
- v0.0.7-0.20230829141010-ad3c96069fc8 29 Aug 2023
- v0.0.6 12 Apr 2023
- v0.0.5 05 Apr 2023
- v0.0.5-0.20230404174214-4d6fd58a18ad 04 Apr 2023
- v0.0.4 01 Mar 2023
- v0.0.3 01 Mar 2023
- v0.0.2 01 Mar 2023
- v0.0.1 27 Feb 2023
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v0.0.10-0.20250507104347-80610b456b95 | 07 May 2025 | none | Apache-2.0 | — | Details → |
| v0.0.10-0.20250501144321-568ed02f069c | 01 May 2025 | none | Apache-2.0 | — | Details → |
| v0.0.10-0.20241125081959-a81ddd0d44ca | 25 Nov 2024 | none | Apache-2.0 | — | Details → |
| v0.0.10-0.20241015135217-29ca1e77b2c1 | 15 Oct 2024 | none | Apache-2.0 | — | Details → |
| v0.0.10-0.20241011094127-a5cd19832543 | 11 Oct 2024 | none | Apache-2.0 | — | Details → |
| v0.0.10-0.20240627125526-afa23908e3e3 | 27 Jun 2024 | none | Apache-2.0 | — | Details → |
| v0.0.9 | 16 Apr 2024 | none | Apache-2.0 | — | Details → |
| v0.0.9-0.20240415211207-3be10b446750 | 15 Apr 2024 | none | Apache-2.0 | — | Details → |
| v0.0.8 | 15 Apr 2024 | none | Apache-2.0 | — | Details → |
| v0.0.8-0.20240409212435-4bd1afeef43f | 09 Apr 2024 | none | Apache-2.0 | — | Details → |
| v0.0.8-0.20240216161101-9e5ff2e8c589 | 16 Feb 2024 | none | Apache-2.0 | — | Details → |
| v0.0.7 | 16 Jan 2024 | none | Apache-2.0 | — | Details → |
| v0.0.7-0.20240116175916-ec4a6f50fe7d | 16 Jan 2024 | none | Apache-2.0 | — | Details → |
| v0.0.7-0.20231106143248-c0f1d0ca6811 | 06 Nov 2023 | none | Apache-2.0 | — | Details → |
| v0.0.7-0.20231025074516-dddcaf5eba15 | 25 Oct 2023 | none | Apache-2.0 | — | Details → |
| v0.0.7-0.20230829141010-ad3c96069fc8 | 29 Aug 2023 | none | Apache-2.0 | — | Details → |
| v0.0.6 | 12 Apr 2023 | none | Apache-2.0 | — | Details → |
| v0.0.5 | 05 Apr 2023 | none | Apache-2.0 | — | Details → |
| v0.0.5-0.20230404174214-4d6fd58a18ad | 04 Apr 2023 | none | Apache-2.0 | — | Details → |
| v0.0.4 | 01 Mar 2023 | none | Apache-2.0 | — | Details → |
| v0.0.3 | 01 Mar 2023 | none | Apache-2.0 | — | Details → |
| v0.0.2 | 01 Mar 2023 | none | Apache-2.0 | — | Details → |
| v0.0.1 | 27 Feb 2023 | none | Apache-2.0 | — | Details → |
All 23 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/grafana/dataplane/sdata
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/grafana/dataplane/sdata
Is github.com/grafana/dataplane/sdata safe to use?
Vulert has no vulnerabilities on record for github.com/grafana/dataplane/sdata 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/grafana/dataplane/sdata's Vulert package health score?
Vulert scores github.com/grafana/dataplane/sdata 59/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/grafana/dataplane/sdata affected?
No. v0.0.9, 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/grafana/dataplane/sdata should I use?
v0.0.9 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/grafana/dataplane/sdata have?
0 vulnerabilities are recorded for github.com/grafana/dataplane/sdata 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/grafana/dataplane/sdata vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/grafana/dataplane/sdata 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/grafana/dataplane/sdata 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/grafana/dataplane/sdata for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/grafana/dataplane/sdata version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.