theupdateframework / theupdateframework/rust-tuf
Should Client::new download the latest metadata?
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 198
- Forks
- 39
- Avg merge
- 9h 19m
- Merged PRs (30d)
- 2
Description
Copying from #157. Client::new right now starts with the first metadata, but that could be years out of date for a long-lived repository. Should it instead try to download the latest version instead?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Client::new entry point and read the context copied from issue #157. Determine how the initial metadata is selected and what “latest” should mean for a long-lived repository. Done requires an agreed behavior for downloading newer metadata, with coverage for the resulting initialization path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100