Consider dependency on bincode

Open
  • Is something wrong?
#33 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust
Domain
security

Research direction

The issue names no files, tests, or entry points; start by locating the crate's use of bincode and reviewing the dependency's maintenance status. Determine whether avoiding a bincode-based format is feasible without destabilising certificate infrastructure, then document the chosen direction and its impact.

Written by the indexing model from the issue text.

Description

Given the unclear maintenance status of this crate, it may be desirable to avoid stabilising on a format that uses this encoding.

Dominant language
Rust
Stars
181
Forks
14
Avg merge
14h 16m
Merged PRs (30d)
21

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rustls/upki

All issues in rustls/upki

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.