Summary
Fixes #45.
Adds a global --local option that uses ./.opensrc in the current project
instead of the default global ~/.opensrc cache.
The default behavior is unchanged, and OPENSRC_HOME continues to work when
--local is not used. The local cache contains its own .gitignore, so fetched
sources do not pollute the parent repository's Git status.
Testing
cargo fmt --manifest-path cli/Cargo.toml -- --checkcargo test --manifest-path cli/Cargo.tomlcargo clippy --manifest-path cli/Cargo.toml -- -D warningscargo build --release --manifest-path cli/Cargo.toml- project-local CLI smoke in a temporary Git repository
Activity
4The security-review bot links to an internal Slack thread that I cannot access. Could you share any actionable findings on the PR so I can address them? The current internal-security check is neutral; I am not interpreting that as a confirmed pass. The Vercel deployment also requires authorization from a member of your team.
Kind regards, Hristos
On Sat, 07 Nov 2026 14:28:02 -0800, "vercel-internal-security-reviewer[bot]" @.***> wrote:
vercel-internal-security-reviewer[bot] left a comment (vercel-labs/opensrc#73)
-- Reply to this email directly or view it on GitHub: https://github.com/vercel-labs/opensrc/pull/73#issuecomment-6713858490 You are receiving this because you were mentioned.
Message ID: @.***>
@ChrisX101010 is attempting to deploy a commit to the Vercel Labs Team on Vercel.
A member of the Team first needs to authorize it.