hyperlight-dev / hyperlight-dev/hyperlight-sandbox
JavaScript backend integration for scoped HTTP credentials
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 73
- Forks
- 7
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 23
Description
Follow-up from #89 (Scoped credentials for outgoing HTTP).
The JavaScript backend currently accepts the CredentialRegistry parameter but ignores it (parameter prefixed _); the WIT attach call is not honoured on the JS dispatch path and no header is injected.
The JS backend needs the same host-side outgoing-handler wiring as the Wasm backend so that attach is honoured and the credential header is injected at dispatch time.
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
Compare the JavaScript backend dispatch path with the Wasm backend's host-side outgoing-handler wiring, focusing on the accepted CredentialRegistry parameter and the WIT attach call. Done means attach is honored on the JavaScript path and the credential header is injected at dispatch time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rust, wasm
- Domain
- backend, networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100