# RUSTSEC-2022-0060: orbtk is Unmaintained

> The orbtk crate is unmaintained, posing supply chain risks; developers should migrate to alternatives like iced or slint.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 13 Oct 2022

## What is RUSTSEC-2022-0060?

RUSTSEC-2022-0060 is a vulnerability in orbtk, published on 13 Oct 2022. 

### Official description

The `orbtk` crate is no longer maintained.

Alternatives proposed by the authors:

 * [`iced`](https://crates.io/crates/iced)
 * [`slint`](https://crates.io/crates/slint)

## Which versions are affected by RUSTSEC-2022-0060?

1 open source package ship an affected version, including orbtk.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `orbtk` | crates.io | From 0.0.0-0 | None |

## How do I fix RUSTSEC-2022-0060?

No fix has been published for RUSTSEC-2022-0060 yet. Limit exposure of the affected software until one is available.

## Is RUSTSEC-2022-0060 being exploited?

There is no known exploitation of RUSTSEC-2022-0060 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2022-0060 and fix it if it is affected.

What it is: RUSTSEC-2022-0060 is a vulnerability in orbtk, published on 13 Oct 2022. 
Exploitation: There is no known exploitation of RUSTSEC-2022-0060 in the wild and no public exploit code.

Affected packages and fixed versions:
- orbtk (crates.io): affected from 0.0.0-0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2022-0060/ (Markdown: https://insights.sbomify.com/RUSTSEC-2022-0060/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2022-0060

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2022-0060/
Summaries are generated and may contain mistakes; the official description above is the record.