Common MSBuild sandboxing
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1k
- Forks
- 167
- PR merge metrics
- No merged PRs in 30d
Description
Hi everyone,
it's a while back that I've discovered BuildXL, and due to its sandboxing infrastructure, my initial thought was that this could be used as a common sandboxing approach when cloning third-party repositories without worrying about security too much (at least file access). I'm not entirely sure if that's the scope of the project. Back then I at least had to install some system component to make it work on macOS.
Could someone give some clarification and a few pointers?
Contributor guide
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 by reviewing BuildXL's existing sandboxing scope and the macOS system component mentioned in the issue. Clarify whether a common sandboxing approach for cloning third-party repositories is within project scope, then document the relevant pointers and expected security boundaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- operating-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100