Artifact Signing
13
Total Pages
10
Linux-Friendly Pages
3
Pages with Bias
23.1%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
44 issues found
Showing 1-25 of 44 flagged pages
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation heavily focuses on Windows-specific tools (SignTool, MSI installers, WinGet, PowerShell) and provides detailed setup instructions only for Windows environments. There are no equivalent Linux/macOS instructions or examples for Artifact Signing integration, and Windows tools are mentioned first and exclusively in critical setup sections.
Recommendations
- Add explicit instructions or examples for Linux/macOS users, such as using cross-platform .NET tools or SDKs.
- Document how to use Artifact Signing with open-source signing tools available on Linux (e.g., osslsigncode, gpg, or .NET CLI).
- Clarify which integrations (GitHub Actions, Azure DevOps, SDK) are cross-platform and provide sample workflows for Linux/macOS.
- Mention any limitations or Windows-only requirements up front, and provide alternatives or workarounds for non-Windows users.
- Include parity tables or sections comparing Windows and Linux/macOS setup steps for each integration.
Create Pull Request
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page is heavily focused on Windows-specific tools and workflows, particularly SignTool, PowerShell, and Windows SDK components. All setup instructions, examples, and prerequisites are Windows-centric, with no mention of Linux/macOS alternatives or cross-platform signing methods. While other integrations (GitHub Actions, Azure DevOps, SDK) are listed, only Windows/PowerShell workflows are detailed. Linux/macOS users are left without guidance for equivalent signing tasks.
Recommendations
- Add explicit instructions and examples for Linux/macOS users, including supported signing tools and workflows.
- Clarify whether Artifact Signing supports cross-platform signing and, if so, provide guidance for non-Windows environments.
- Include sample commands for Linux (e.g., using OpenSSL, GPG, or other relevant tools if supported).
- Document any limitations or platform requirements for each integration, so users know which are Windows-only.
- For GitHub Actions and Azure DevOps, show how to use these integrations from Linux runners if possible.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page heavily focuses on Windows-specific tools and workflows, especially SignTool, with all setup instructions, prerequisites, and examples tailored exclusively for Windows environments. PowerShell is used for all command-line examples, and Windows installation methods (MSI, Setup.exe, winget) are emphasized. No Linux/macOS equivalents or cross-platform guidance are provided for SignTool integration, and there is no mention of alternative signing tools or workflows for non-Windows users.
Recommendations
- Clearly indicate if SignTool integration is Windows-only; if not, provide equivalent instructions for Linux/macOS users, including supported signing tools and setup steps.
- For GitHub Actions, Azure DevOps, and SDK integrations, add explicit cross-platform examples and clarify OS compatibility.
- If PowerShell is not available on Linux/macOS for these tasks, suggest alternative shell commands or tools.
- Add a section summarizing platform support for each integration, so users know which are Windows-only and which are cross-platform.
- Where possible, provide Linux/macOS installation instructions for .NET runtime and any required libraries.
- Highlight any limitations or workarounds for Linux/macOS users.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page heavily focuses on Windows-specific tools and workflows, especially SignTool, with all setup instructions, prerequisites, and examples tailored exclusively for Windows environments. PowerShell is used for all command-line examples, and Windows installation methods (MSI, Setup.exe, winget) are emphasized. There are no Linux/macOS equivalents or guidance for non-Windows users, even though some integrations (GitHub Actions, Azure DevOps, SDK) could be cross-platform.
Recommendations
- Clearly indicate if SignTool integration is Windows-only, and provide alternative signing workflows for Linux/macOS users where possible.
- For cross-platform integrations (GitHub Actions, Azure DevOps, SDK), add explicit Linux/macOS setup instructions and examples.
- If Artifact Signing supports non-Windows signing tools (e.g., OpenSSL, GPG, or other CLI tools), document their usage.
- For PowerShell-heavy sections, offer Bash or shell script equivalents for Linux/macOS users.
- Add a section summarizing platform support and limitations up front, so users know if Windows is required for certain integrations.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation heavily focuses on Windows-specific tools and workflows, particularly SignTool and PowerShell, with detailed setup instructions and examples exclusively for Windows environments. There are no equivalent Linux/macOS instructions or examples for Artifact Signing integration, and Windows tools (SignTool, MSI installer, winget) are mentioned first and exclusively. Other integrations (GitHub Actions, Azure DevOps, SDK) are referenced but not explained in detail, and no Linux/macOS signing tool guidance is provided.
Recommendations
- Add explicit instructions and examples for integrating Artifact Signing with Linux/macOS signing tools (e.g., OpenSSL, GPG, codesign for macOS).
- Provide parity in setup steps for Linux/macOS, including how to install required SDKs and dependencies.
- Include sample scripts or commands for Linux/macOS environments alongside PowerShell/Windows examples.
- Clarify which integrations are cross-platform and provide links or guidance for Linux/macOS users.
- Consider restructuring the page so that cross-platform integrations (GitHub Actions, SDK) are presented before Windows-only tools.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page heavily focuses on Windows-specific tools and workflows, especially SignTool, with all setup instructions, prerequisites, and examples tailored to Windows environments. Installation steps rely on Windows Package Manager (winget), MSI installers, and PowerShell commands. There are no Linux/macOS equivalents or instructions for using Artifact Signing with non-Windows signing tools. While other integrations (GitHub Actions, Azure DevOps, SDK) are mentioned, their setup is not detailed, and Windows is prioritized throughout.
Recommendations
- Add explicit instructions and examples for using Artifact Signing on Linux/macOS, including supported signing tools (e.g., OpenSSL, GPG, or Linux equivalents if available).
- Provide parity for installation steps, such as using package managers like apt, yum, or Homebrew, and shell script examples instead of only PowerShell.
- Clarify which integrations are cross-platform and provide detailed setup guides for GitHub Actions, Azure DevOps, and SDK usage on Linux/macOS.
- Mention any limitations or Windows-only aspects up front, and link to Linux/macOS guidance where applicable.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows, with all setup instructions, prerequisites, and examples tailored exclusively to Windows environments. It assumes the use of Windows tools (SignTool.exe, MSI installers, WinGet, PowerShell) and does not provide equivalent instructions or examples for Linux or macOS users. Alternative integrations (GitHub Actions, Azure DevOps, SDK) are mentioned but not documented in detail on this page.
Recommendations
- Add explicit guidance or examples for Linux/macOS users where possible, especially for SDK-based signing or CI integrations.
- Clarify early in the document if SignTool-based integration is Windows-only, and direct Linux/macOS users to supported alternatives (e.g., GitHub Actions, SDK).
- Provide parity in documentation for non-Windows platforms, such as step-by-step guides for using Artifact Signing via GitHub Actions or the SDK on Linux/macOS.
- If certain integrations are Windows-only, clearly label those sections as such and provide links to cross-platform alternatives.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page heavily focuses on Windows-specific tools and workflows, particularly SignTool, PowerShell, and Windows SDK dependencies. All setup instructions, examples, and installation steps are Windows-centric, with no mention of Linux/macOS equivalents or cross-platform alternatives for Artifact Signing. The only integrations with potential cross-platform support (GitHub Actions, Azure DevOps, SDK) are referenced briefly and externally, without detailed parity instructions.
Recommendations
- Provide explicit guidance for Linux/macOS users, including supported signing tools, installation steps, and examples.
- Clarify whether Artifact Signing supports non-Windows signing workflows and, if so, document them with equal detail.
- Add examples for using Artifact Signing SDK on Linux/macOS, including sample commands and environment setup.
- If SignTool is Windows-only, highlight alternative cross-platform signing tools (e.g., OpenSSL, GPG, or platform-agnostic SDK usage) and how they can integrate with Artifact Signing.
- Ensure that GitHub Actions and Azure DevOps instructions include Linux/macOS runners and relevant configuration details.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page heavily focuses on Windows-specific tools and workflows, particularly SignTool, MSI installers, WinGet, and PowerShell commands. All setup instructions and examples are for Windows environments, with no mention of Linux/macOS equivalents or cross-platform alternatives. While other integrations (GitHub Actions, Azure DevOps, SDK) are listed, their setup is not detailed here, and the primary walkthrough is Windows-only.
Recommendations
- Add explicit guidance for Linux/macOS users, including whether Artifact Signing can be used from these platforms and how.
- If SignTool is Windows-only, clarify this early and direct Linux/macOS users to supported cross-platform integrations (e.g., GitHub Actions, SDK).
- Provide example workflows for GitHub Actions, Azure DevOps, and SDK usage on Linux/macOS, including installation and invocation steps.
- Mention any limitations or alternative signing tools for non-Windows environments.
- Reorganize the page to present cross-platform options before or alongside Windows-specific instructions.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page is heavily focused on Windows-specific tools and workflows, particularly SignTool, PowerShell, and Windows SDK components. All setup instructions, installation steps, and examples are exclusively for Windows environments, with no mention of Linux/macOS equivalents or cross-platform alternatives. The main integration described is SignTool, which is a Windows-only tool, and all installation commands are Windows-centric (MSI, Setup.exe, winget, PowerShell). Other integrations (GitHub Actions, Azure DevOps, SDK) are briefly referenced but lack detailed cross-platform guidance.
Recommendations
- Add explicit guidance and examples for Linux/macOS users, especially for integrations like GitHub Actions, Azure DevOps, and the Artifact Signing SDK.
- Clarify which integrations are cross-platform and provide step-by-step instructions for non-Windows environments.
- If SignTool is Windows-only, highlight alternative signing tools or workflows for Linux/macOS users, or state clearly that SignTool integration is Windows-specific.
- Include installation and usage examples for the Artifact Signing SDK on Linux/macOS, and describe how to use it for signing artifacts.
- Where PowerShell is used, offer Bash or shell script equivalents for Linux/macOS users where possible.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page is heavily focused on Windows-specific tools and workflows, especially SignTool, PowerShell, and Windows SDK. All setup instructions, prerequisites, and examples are Windows-centric, with no mention of Linux/macOS equivalents or cross-platform alternatives for Artifact Signing. The use of MSI installers, WinGet, and PowerShell commands further reinforces the Windows bias. While other integrations (GitHub Actions, Azure DevOps, SDK) are mentioned, their setup is not detailed, and the primary walkthrough is Windows-only.
Recommendations
- Add explicit instructions and examples for Linux/macOS users, including how to use Artifact Signing with cross-platform tools.
- Document any available CLI or SDK-based signing workflows that work on Linux/macOS, or clarify platform limitations.
- Provide parity in setup steps for non-Windows environments, such as using .NET Core CLI, zip/tar installers, or alternative signing tools.
- Clarify in the prerequisites and introduction whether SignTool integration is Windows-only, and highlight cross-platform options where possible.
- Expand the GitHub Actions and Azure DevOps sections with step-by-step examples for Linux/macOS runners.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page is heavily focused on Windows, especially in the SignTool integration section. All examples, prerequisites, and installation instructions are Windows-specific, using tools like SignTool.exe, PowerShell, MSI installers, and Windows Package Manager (winget). There are no Linux or macOS equivalents or instructions for setting up Artifact Signing with non-Windows tools. While other integrations (GitHub Actions, Azure DevOps, SDK) are mentioned, their instructions are deferred to external links and not detailed here, and the primary walkthrough is Windows-only.
Recommendations
- Add explicit instructions or examples for Linux/macOS users, especially for GitHub Actions, Azure DevOps, and SDK integrations.
- Clarify which integrations are cross-platform and provide parity in documentation (e.g., show how to use Artifact Signing from Linux build agents or macOS).
- If SignTool is Windows-only, state this clearly and provide alternative signing tools or workflows for Linux/macOS users.
- Include sample scripts or commands for Linux/macOS environments where possible (e.g., using dotnet CLI, bash, or other cross-platform tools).
- Document any limitations or platform requirements for each integration up front.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows, especially in the main 'Set up SignTool to use Artifact Signing' section. All setup instructions, prerequisites, and examples assume a Windows environment, referencing Windows-only tools (SignTool, MSI installers, WinGet, PowerShell, Visual C++ Redistributable). There are no Linux or macOS equivalents or alternative instructions provided for the core signing workflow. Other integrations (GitHub Actions, Azure DevOps, SDK) are mentioned, but not documented in detail here.
Recommendations
- Clearly state at the beginning if SignTool integration is Windows-only, and direct Linux/macOS users to alternative integrations (e.g., GitHub Actions, SDK).
- For each integration, specify platform support and provide parity in setup instructions/examples for Linux/macOS where possible.
- If Artifact Signing supports Linux/macOS workflows (e.g., via SDK, GitHub Actions), add explicit sections or links with step-by-step instructions for those platforms.
- For PowerShell or WinGet commands, offer equivalent Bash or shell commands if supported, or clarify that these are Windows-only.
- Summarize all supported platforms and tools in a table at the top, with links to relevant setup guides for each OS.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page heavily focuses on Windows-specific tools and workflows, especially SignTool, with all setup instructions, prerequisites, and examples tailored exclusively for Windows environments. PowerShell commands and Windows installers are provided, while Linux/macOS equivalents, alternative signing tools, or cross-platform guidance are absent. Other integrations (GitHub Actions, Azure DevOps, SDK) are only briefly mentioned without platform-specific instructions, leaving Linux/macOS users with unclear guidance.
Recommendations
- Add explicit instructions and examples for using Artifact Signing with Linux/macOS, including supported signing tools (e.g., OpenSSL, GPG, or cross-platform .NET tools) if available.
- Clarify which integrations (GitHub Actions, Azure DevOps, SDK) are cross-platform and provide Linux/macOS setup steps and sample workflows.
- If SignTool is Windows-only, highlight alternative signing approaches for Linux/macOS users, or state clearly that SignTool integration is not supported outside Windows.
- Provide parity in authentication and configuration examples for non-Windows environments.
- Include troubleshooting or limitations sections for Linux/macOS users.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation for setting up signing integrations with Artifact Signing is heavily focused on Windows environments. The primary integration described is SignTool, which is a Windows-only tool, and all setup instructions, examples, and installation steps are tailored for Windows users. PowerShell commands are used exclusively for installation and configuration, and Windows-specific package managers (winget, MSI installers) are referenced. There are no equivalent instructions or examples for Linux or macOS users, nor is there mention of cross-platform alternatives for signing artifacts.
Recommendations
- Add explicit notes clarifying platform support for each integration, especially where Windows-only tools are required.
- Provide Linux/macOS alternatives or guidance for artifact signing, such as using OpenSSL, GPG, or cross-platform .NET tools if supported.
- Include examples for setting up signing integrations on Linux/macOS, or clarify if these platforms are not supported.
- For GitHub Actions and Azure DevOps, highlight any platform-agnostic usage or provide sample workflows for Linux runners.
- If Artifact Signing SDK supports cross-platform usage, add setup and usage instructions for Linux/macOS environments.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation for setting up signing integrations with Artifact Signing is heavily Windows-centric, especially in the SignTool section. All setup instructions, prerequisites, and examples are tailored for Windows environments, using Windows-specific tools (SignTool.exe, MSI installers, WinGet, PowerShell). There are no equivalent instructions or examples for Linux or macOS users, nor is there guidance for cross-platform alternatives. The other integrations (GitHub Actions, Azure DevOps, SDK) are mentioned but not documented in detail here.
Recommendations
- Add explicit guidance for Linux/macOS users, including supported signing tools and setup steps.
- If SignTool is Windows-only, clarify this early and direct non-Windows users to alternative integrations (e.g., SDK, GitHub Actions).
- Provide examples for using Artifact Signing with cross-platform tools (e.g., OpenSSL, sigstore, or .NET CLI on Linux/macOS if supported).
- Ensure parity in documentation for SDK usage, including Linux/macOS installation and usage instructions.
- Where PowerShell is used for automation, offer equivalent Bash or shell script examples for Linux/macOS.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page is heavily focused on Windows, with all setup instructions, prerequisites, and examples centered around Windows tools (SignTool.exe, MSI installers, WinGet, PowerShell). There are no instructions or examples for Linux or macOS users, nor is there mention of equivalent signing workflows or tools for non-Windows platforms. The only integrations described in detail are Windows-specific, and even general integrations (GitHub Actions, Azure DevOps) are referenced only via external links without parity in setup instructions.
Recommendations
- Add explicit guidance for Linux/macOS users, including supported signing tools and workflows if available.
- Clarify whether Artifact Signing is Windows-only or if cross-platform support is planned or available.
- Provide examples for using Artifact Signing in Linux/macOS CI environments (e.g., with GitHub Actions, Azure DevOps pipelines running on Linux agents).
- If SignTool is Windows-only, highlight alternative signing methods for non-Windows platforms, or state limitations clearly.
- Include installation and usage instructions for the Artifact Signing SDK on Linux/macOS, if supported.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily Windows-centric, especially in the SignTool integration section. All setup instructions, prerequisites, and examples are for Windows environments, using Windows-specific tools (SignTool.exe, MSI installers, WinGet, PowerShell). There are no Linux/macOS equivalents or alternative signing tool instructions provided. Other integrations (GitHub Actions, Azure DevOps, SDK) are mentioned but not documented in detail here.
Recommendations
- Add explicit guidance for Linux/macOS users, including supported signing tools and setup instructions.
- If SignTool is Windows-only, clarify its platform limitations and direct Linux/macOS users to alternative integrations (e.g., SDK, GitHub Actions).
- Provide step-by-step examples for setting up Artifact Signing with GitHub Actions, Azure DevOps, and the SDK, including Linux/macOS runners.
- List platform compatibility for each integration at the top of the article.
- Where possible, offer cross-platform installation instructions (e.g., .NET runtime, SDK usage).
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation for setting up signing integrations with Artifact Signing is heavily focused on Windows. The main integration described in detail is SignTool, which is a Windows-only tool. All installation instructions, examples, and prerequisites are Windows-centric, using PowerShell, MSI installers, WinGet, and referencing Windows SDK components. There are no Linux or macOS equivalents or alternative signing tool instructions provided, nor is there guidance for using Artifact Signing from non-Windows environments. Other integrations (GitHub Actions, Azure DevOps, SDK) are mentioned only briefly and without platform-specific setup details.
Recommendations
- Add explicit guidance or examples for Linux/macOS users, such as how to use Artifact Signing via the SDK, CLI, or other cross-platform tools.
- If SignTool is Windows-only, clarify this early and direct Linux/macOS users to supported alternatives (e.g., SDK, GitHub Actions, Azure DevOps).
- Provide setup instructions for Artifact Signing using the SDK on Linux/macOS, including installation and usage examples.
- Include a table or section comparing platform support for each integration, so users know which options are available for their OS.
- Where possible, provide shell (bash) examples alongside PowerShell commands.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page is heavily focused on Windows-specific tools and workflows, particularly SignTool, PowerShell, and Windows installers (MSI, Setup.exe, winget). All setup instructions, examples, and prerequisites for the main integration (SignTool) are Windows-only, with no mention of Linux/macOS alternatives or cross-platform signing tools. Other integrations (GitHub Actions, Azure DevOps, SDK) are referenced but not documented in detail, and no Linux/macOS-specific signing guidance is provided.
Recommendations
- Clearly indicate that SignTool integration is Windows-only, and provide guidance for Linux/macOS users on alternative signing methods or integrations.
- Add explicit sections or examples for Linux/macOS users, such as using the Artifact Signing SDK, GitHub Actions, or Azure DevOps pipelines from non-Windows environments.
- Document cross-platform signing workflows, including how to use Artifact Signing from Linux/macOS CI runners or developer machines.
- If possible, provide parity for installation and usage instructions for the Artifact Signing SDK or other integrations on Linux/macOS.
- List platform compatibility for each integration at the top of the page, so users can quickly identify which options are available for their OS.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page is heavily focused on Windows-specific tools and workflows, particularly SignTool, MSI installers, WinGet, and PowerShell commands. All setup instructions and examples for Artifact Signing client tools are exclusively for Windows environments, with no mention of Linux or macOS alternatives or equivalent signing workflows. While other integrations (GitHub Actions, Azure DevOps, SDK) are listed, the detailed guidance is only for Windows/SignTool.
Recommendations
- Add explicit instructions or examples for setting up Artifact Signing on Linux/macOS, including supported signing tools (e.g., OpenSSL, GPG, or platform-agnostic .NET tools) if available.
- Clarify whether SignTool integration is Windows-only, and if so, provide parity by expanding detailed setup guides for other integrations (e.g., GitHub Actions, Azure DevOps) that work cross-platform.
- Include Linux/macOS installation commands for the .NET runtime and Artifact Signing SDK/dlib, using package managers like apt, yum, brew, etc.
- If Artifact Signing is not supported on Linux/macOS for certain workflows, state this explicitly to set user expectations.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased toward Windows, with all setup instructions, prerequisites, and examples focused exclusively on Windows tools (SignTool, PowerShell, WinGet, MSI installers). There are no instructions or examples for Linux or macOS users, nor are cross-platform alternatives mentioned for the core signing workflow. The only integrations that might be cross-platform (GitHub Actions, SDK) are referenced briefly with external links, but the main guide is Windows-centric.
Recommendations
- Provide equivalent setup and usage instructions for Linux and macOS, including supported signing tools and installation steps.
- Include examples using cross-platform command-line tools (e.g., OpenSSL, GPG, or platform-agnostic SDK usage) where possible.
- Clarify which integrations (e.g., GitHub Actions, SDK) are cross-platform and provide direct, in-page examples for non-Windows environments.
- List platform requirements and limitations up front, and offer guidance for users on unsupported platforms.
- If SignTool is Windows-only, suggest alternative signing workflows for Linux/macOS users, or explicitly state the limitation.
Artifact Signing
Device Guard Signing Service migration to Artifact Signing
...gning/how-to-device-guard-signing-service-migration.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily Windows-centric, with all examples, commands, and tooling (e.g., PowerShell, SignTool, MSIX Packaging Tool, mountvol.exe, Event Viewer) being Windows-specific. There are no Linux or macOS equivalents, nor any mention of how to perform migration or signing tasks on non-Windows platforms. Windows paths and UI instructions are used throughout, and all deployment and verification steps assume a Windows environment.
Recommendations
- Add equivalent instructions for Linux/macOS environments, including how to access and manipulate CI policies if supported.
- Provide cross-platform signing tool examples (e.g., OpenSSL, Azure CLI, or REST API usage) for Artifact Signing.
- Clarify whether Artifact Signing and CI policy deployment are supported or relevant for non-Windows OS, and if not, state this explicitly.
- If the migration is only applicable to Windows, add a prominent note at the top of the documentation.
- Where possible, use platform-neutral language and provide parity in examples and tooling.
Artifact Signing
Sign a CI policy by using Artifact Signing
...ain/articles/artifact-signing/how-to-sign-ci-policy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows, with all examples and prerequisites focused on PowerShell and Windows-specific paths and tooling. There are no Linux/macOS instructions, and the guidance assumes the use of Windows Defender Application Control, further reinforcing the Windows-centric approach.
Recommendations
- Provide equivalent instructions and examples for Linux/macOS environments, including shell commands (e.g., Bash) and file paths.
- Clarify whether the Az.TrustedSigning module and Artifact Signing service can be used cross-platform, and document any platform-specific limitations.
- Include installation instructions for Azure PowerShell on Linux/macOS, and verify that all commands work in those environments.
- Reference cross-platform deployment scenarios, not just Windows Defender Application Control.
- Explicitly note any Windows-only features or steps, and suggest alternatives for non-Windows users where possible.
Artifact Signing
Device Guard Signing Service migration to Artifact Signing
...gning/how-to-device-guard-signing-service-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily Windows-centric, with all examples, file paths, and tooling (e.g., PowerShell, SignTool, mountvol.exe, Event Viewer) specific to Windows. There are no Linux or macOS equivalents provided, nor any mention of how to perform similar tasks on non-Windows platforms. All migration scenarios and deployment steps assume a Windows environment, and the related content is exclusively Windows-focused.
Recommendations
- Add explicit statements about platform support: clarify if Artifact Signing and CI policy management are Windows-only, or provide guidance for Linux/macOS users if supported.
- Include Linux/macOS equivalents for file operations (e.g., deleting files, mounting EFI partitions), signing tools, and verification steps.
- Provide cross-platform command examples, such as Bash scripts or references to open-source signing tools compatible with Linux/macOS.
- If PowerShell is required, note how to install and use PowerShell Core on Linux/macOS, or provide alternative instructions.
- Reference any Azure CLI or REST API methods for Artifact Signing that are platform-agnostic.
- Add a section addressing migration for environments that include non-Windows endpoints, if applicable.