Rebase the vendored biscuit fork onto biscuit-rust 7.0, and pin Ed25519
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- authentication, security
Research direction
Read the vendored fork in third_party against upstream biscuit-rust 7.0.0-alpha.3, starting with block_datalog, the biscuit-parser bump, and the load path exercised by hostile.rs. Run the token round-trip and hostile-input tests, then follow any from_with_limits adoption to the error substrings hostile.rs asserts; properties.rs:329 shows where unsafe-protobuf-access is needed. Done means the fork builds, existing wicket tokens still load, and structure::check plus the hostile/error tests pass.
Written by the indexing model from the issue text.
Description
From reading biscuit-rust (2026-11-15). The vendored fork (third_party, 6.0.0-fork.0) is at upstream main aa5a672, two days before 7.0.0-alpha.1, so most of 7.0's breaks are already in. What's left, up to alpha.3:
- blocks are parsed once, and a block referring to a symbol defined later is rejected;
- legacy third-party blocks no longer load;
DeserializationLimits/BlockLimitsare new;- the protobuf types sit behind
unsafe-protobuf-access(needed for properties.rs:329).
The wire format is unchanged, so tokens wicket mints still load.
Rebase work: block_datalog needs about 15 lines rewritten, and biscuit-parser goes to 0.3.0-alpha.1. If load adopts from_with_limits, map the error substrings hostile.rs asserts.
What it buys: pinning Ed25519 through the limits; structure::check stays. 7.0 still has no parser for a lone third-party (grant) block.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 43m
- Merged PRs (30d)
- 190
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
- 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.
More from public/wicket
-
Don't break the machines: node health alerts, admission control, reserved headroom, volume lifecycle, collection trackingPossibly taken @public claimed this today. Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
enhancement parked
Difficulty 5/5 Over a week Newbie friendliness 12/100
public/wicket#371 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 12/100
Maintainers usually reply within 1 day
-
Windowed egress caps and standard OTLP decision records (from AgentCore, Strands Box and Dogwood)Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 22/100
Maintainers usually reply within 1 day
Similar issues
-
crate: spate-kafka priority: low tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
macOS 菜单栏托盘图标保留橙色,与系统单色图标风格不一致Possibly taken @xhugoliu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
YizhengWw/HachimoDock#56 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area:ui bug effort:low P2 source:agent
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day