Skip to content

docs: add guidance on pinning a commit hash for security purposes #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
samuelmatos-s1 merged 2 commits into from
Mar 30, 2026
Merged

docs: add guidance on pinning a commit hash for security purposes #21

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1102612
trivial: add guidance on pinning a commit hash for security purposes
samuelmatos-s1 Mar 30, 2026
4cbf320
trivial: add guidance on pinning a commit hash for security purposes
samuelmatos-s1 Mar 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,18 @@ export PURPLEMCP_CONSOLE_BASE_URL="https://your-console.sentinelone.net"
uvx --from git+https://github.com/Sentinel-One/purple-mcp.git purple-mcp --mode=stdio
```

#### ⚠️ Security note ⚠️

For production or security-sensitive environments, pin to a specific commit hash
instead of using the default branch to reduce supply chain risk from the our
[releases](https://github.com/Sentinel-One/purple-mcp/releases) or our verified
commits in [main](https://github.com/Sentinel-One/purple-mcp/commits/main) branch.

```bash
# Run with pinned hash
uvx --from git+https://github.com/Sentinel-One/purple-mcp.git@<commit-hash> purple-mcp --mode=stdio
```

### Using Docker

```bash
Expand Down
Loading