Vulnerability Database · crates.io · Package report
field-offset: vulnerability history, versions and safety
field-offset is a package in the crates.io ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the crates.io ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on field-offset 0.3.6 i
Updated on 23 Oct 2026
Good news: 0.3.6, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Niche
- Community Inactive
What to do: Stay on 0.3.6 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.3.6 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 0.3.6 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 262 packages i
- Stars 35 i
- OpenSSF scorecard 2/10 i
- Last release 40 months ago i
- Licence Apache-2.0 OR MIT i
Version list, release dates, licence and dependants published by crates.io, 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 field-offset, 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.
- 0.3.6 02 Jun 2023
- 0.3.5 04 Mar 2023
- 0.3.4 12 May 2021
- 0.3.3 10 Feb 2021
- 0.3.2 24 Aug 2020
- 0.3.1 22 May 2020
- 0.3.0 16 Mar 2020
- 0.2.0 07 Feb 2020
- 0.1.1 02 May 2016
- 0.1.0 02 May 2016
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 0.3.6 | 02 Jun 2023 | none | Apache-2.0 OR MIT | — | Details → |
| 0.3.5 | 04 Mar 2023 | none | Apache-2.0 OR MIT | — | Details → |
| 0.3.4 | 12 May 2021 | none | Apache-2.0 OR MIT | — | Details → |
| 0.3.3 | 10 Feb 2021 | none | Apache-2.0 OR MIT | — | Details → |
| 0.3.2 | 24 Aug 2020 | none | Apache-2.0 OR MIT | — | Details → |
| 0.3.1 | 22 May 2020 | none | Apache-2.0 OR MIT | — | Details → |
| 0.3.0 | 16 Mar 2020 | none | Apache-2.0 OR MIT | — | Details → |
| 0.2.0 | 07 Feb 2020 | none | Apache-2.0 OR MIT | — | Details → |
| 0.1.1 | 02 May 2016 | none | Apache-2.0 OR MIT | — | Details → |
| 0.1.0 | 02 May 2016 | none | — | — | Details → |
All 10 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 field-offset
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 field-offset
Is field-offset safe to use?
Vulert has no vulnerabilities on record for field-offset in crates.io 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 field-offset's Vulert package health score?
Vulert scores field-offset 55/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 field-offset affected?
No. 0.3.6, 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 field-offset should I use?
0.3.6 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 field-offset have?
0 vulnerabilities are recorded for field-offset in the crates.io 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 field-offset vulnerabilities disclosed?
0 vulnerabilities were recorded for field-offset 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 field-offset 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 field-offset for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the field-offset version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.