Reading the repo
Opening the box…
Reading the repo
Opening the box…
How to install on Linux
Guardian spirit for your repos — a PowerShell module that audits GitHub repos and orgs for supply chain risks by mapping every finding to a real-world attack campaign.
GitHub didn't answer, so this is the saved copy from 13 h ago
Will it work on Linux?
Fylgyr targets github.com. GitHub Enterprise Server (GHES) is not supported in v1.x — API path differences (/api/v3/) and feature-availability variance make it a v2.0 goal. Fylgyr may incidentally work against GHES for a subset of checks; this configuration is not tested or supported.
The maintainers included scripts/install-hooks.ps1. Run it from the cloned folder after reading it.
powershell -ExecutionPolicy Bypass -File .\scripts\install-hooks.ps1
Prerequisites:
- PowerShell 7+
- GitHub token for scans (for local runs, use a fine-grained Personal Access Token (PAT))
- Optional (only for provenance verification): GitHub CLI (
gh)- Windows install for GitHub CLI:
winget install --id GitHub.cli --exact
# Install from PowerShell Gallery
Install-Module Fylgyr
# Provide a GitHub token (required for local runs, this is typically a fine-grained PAT)
$env:GITHUB_TOKEN = Read-Host -Prompt 'GitHub PAT' -MaskInput
# Scan a single repository
Invoke-Fylgyr -Owner 'myorg' -Repo 'myrepo'
# Scan all repositories in an organization
Invoke-Fylgyr -Owner 'myorg'
# Scan organization repositories + org-level policy controls (opt-in)
Invoke-Fylgyr -Owner 'myorg' -IncludeOrgChecks
# Optional cleanup
Remove-Item Env:GITHUB_TOKEN -ErrorAction SilentlyContinue
Why cleanup? Removing token variables after use reduces accidental exposure in later commands, logs, child processes, and shared terminal output.
Requires PowerShell 7+ and a GitHub token. For local runs, this is typically a fine-grained PAT. In GitHub Actions, the built-in
GITHUB_TOKENcan run workflow-file checks. Fylgyr reads$env:GITHUB_TOKENby default, or you can pass-Tokenexplicitly:# Preferred: load from SecretManagement (or your secret manager) # and pass the token directly for this invocation $token = Get-Secret -Name 'FYLGYR_PAT' -AsPlainText Invoke-Fylgyr -Owner 'myorg' -Repo 'myrepo' -Token $token Remove-Variable token -ErrorAction SilentlyContinue # Fallback: masked interactive prompt # $token = Read-Host -Prompt 'GitHub token' -MaskInput # Invoke-Fylgyr -Owner 'myorg' -Repo 'myrepo' -Token $token # Or pass a different token for a single call Invoke-Fylgyr -Owner 'myorg' -Repo 'myrepo' -Token $otherTokenFylgyr strongly recommends fine-grained PATs for default operation. Core repository checks and most organization checks work with least-privilege fine-grained permissions, and no feature requires a classic PAT. Some organization governance APIs (currently PAT policy evidence endpoints) can be restricted by GitHub to GitHub App token types; in those contexts Fylgyr reports advisory
Inforesults instead of a misleading fail. Never hardcode tokens; load them from a secret manager.
Then run bash setup.sh. It stops at the first error and is safe to run again. Servers and tests aren't started; it lists them at the end. Read it first.
Compare yours with the README's “Compatibility” list above before installing anything.
git clone https://github.com/pthoor/fylgyr.git cd fylgyr
In the maintainers' order. Do the README instructions above first — they cover steps outside the terminal.
Install-Module Fylgyr $env:GITHUB_TOKEN = Read-Host -Prompt 'GitHub PAT' -MaskInput Invoke-Fylgyr -Owner 'myorg' -Repo 'myrepo' Invoke-Fylgyr -Owner 'myorg' Invoke-Fylgyr -Owner 'myorg' -IncludeOrgChecks Remove-Item Env:GITHUB_TOKEN -ErrorAction SilentlyContinue $token = Get-Secret -Name 'FYLGYR_PAT' -AsPlainText Invoke-Fylgyr -Owner 'myorg' -Repo 'myrepo' -Token $token Remove-Variable token -ErrorAction SilentlyContinue > > Invoke-Fylgyr -Owner 'myorg' -Repo 'myrepo' -Token $otherToken
No reports for Linux yet.
GitManual AI Agent reads the 6 key files and writes a step-by-step guide for Linux. Once written, it's saved for everyone.