RepoShelf is pre-release software. Security fixes are released only for the latest published Marketplace version, currently 0.1.1. Upgrade to the latest version to receive fixes; earlier versions are not patched.

Do not open a public issue for suspected vulnerabilities. Use GitHub private vulnerability reporting.

Include a concise impact description and reproduction steps using synthetic values. Do not include real PATs, credentials, cookies, private source content, internal hostnames, organization or project names, project IDs, usernames, absolute personnel paths, or ownership-marker contents. If sensitive evidence is essential, first request a secure exchange method in the private report.

You should receive an acknowledgement within seven days. Validation, disclosure, and remediation timelines depend on severity and maintainer availability. Please allow a reasonable remediation window before public disclosure.

RepoShelf handles API credentials, remote content, native Git processes, and managed local workspaces. Changes involving authentication, URL validation, process execution, filesystem containment, ownership markers, or deletion need explicit tests and security review. See the threat model.

Settings that choose where credentials are sent or where files are written, currently reposhelf.instances and reposhelf.cloneRoot, must be readable only from user or remote-machine settings, never from an opened workspace. Changing their scope or how they are read needs the same review.

Native Git clones are bound to the configured instance: a clone URL outside the instance's host and base path needs explicit user confirmation, and the materialization service enforces this independently of the UI. Changes to how clone, fetch, or push targets are chosen need the same review.

The release pipeline is also a security boundary because it holds the Marketplace publishing identity. Changes to the publishing stage, the isolated publishing tool in tools/publish, pipeline credentials, or GitHub Actions pins need the same review. See Marketplace publishing.