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

13 issues found
Showing 1-13 of 13 flagged pages
Artifact Signing Set up signing integrations to use Artifact Signing ...ticles/artifact-signing/how-to-signing-integrations.md
High Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows-based tools and workflows, especially SignTool and PowerShell. All setup instructions, prerequisites, and examples are Windows-specific, with no mention of Linux or macOS alternatives for direct signing. Even in sections referencing cross-platform integrations (e.g., GitHub Actions, Azure DevOps), the details and examples are omitted, and only links are provided. Linux and macOS users are left without guidance for native or CLI-based signing workflows.
Recommendations
  • Add explicit guidance or examples for Linux/macOS users where possible, especially for SDK-based or cross-platform signing scenarios.
  • Clarify early in the document if Artifact Signing with SignTool is Windows-only, and direct non-Windows users to supported alternatives (e.g., GitHub Actions, SDK usage).
  • Expand the 'Use other signing integrations' section with at least one end-to-end example for a non-Windows platform (e.g., using GitHub Actions or the SDK on Linux).
  • If native Linux/macOS CLI tools are not supported, state this clearly and provide recommended workflows for those users.
GitHub 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 →
Scanned: 2026-01-22 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows tools and workflows, especially SignTool, PowerShell, and MSI/WinGet installers. All setup instructions and examples are Windows-specific, with no mention of Linux or macOS equivalents or alternatives. Even in sections about GitHub Actions and Azure DevOps, there are no explicit Linux/macOS instructions or parity notes.
Recommendations
  • Clearly state if Artifact Signing is Windows-only, or if Linux/macOS support is planned or available.
  • If cross-platform support exists (e.g., via GitHub Actions or SDKs), provide explicit Linux/macOS setup instructions and examples.
  • Add notes or sections for Linux/macOS users, including any limitations or alternative tools/workflows.
  • If only Windows is supported for certain integrations (like SignTool), clarify this early in the documentation.
  • For SDK-based integrations, provide cross-platform code samples and installation instructions.
GitHub 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 →
Scanned: 2026-01-16 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows-specific tools and workflows, especially SignTool and PowerShell, with no equivalent instructions or examples for Linux or macOS users. All setup, installation, and usage instructions are Windows-centric, and there is no mention of cross-platform alternatives or guidance for non-Windows environments.
Recommendations
  • Clearly state at the beginning if Artifact Signing with SignTool is Windows-only, and provide guidance for Linux/macOS users if possible.
  • If cross-platform signing is supported (e.g., via the SDK, GitHub Actions, or Azure DevOps), add explicit sections or examples for Linux/macOS environments.
  • Provide installation and usage instructions for Artifact Signing tools on Linux/macOS, or clarify their absence.
  • For GitHub Actions and Azure DevOps, include example workflows that run on Ubuntu/macOS runners, not just Windows.
  • If PowerShell is required, mention cross-platform PowerShell (pwsh) support or alternatives.
  • If only Windows is supported for certain integrations, make this explicit to set expectations.
GitHub 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 →
Scanned: 2026-01-15 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows-specific tools and workflows, particularly SignTool and PowerShell. All setup instructions, installation commands, and examples are for Windows environments, with no mention of Linux or macOS alternatives or parity. Even in sections referencing cross-platform integrations (e.g., GitHub Actions, SDK), no Linux/macOS-specific guidance or examples are provided.
Recommendations
  • Clearly state at the beginning if Artifact Signing integration via SignTool is Windows-only, and provide alternative guidance for Linux/macOS users if available.
  • If cross-platform SDKs or CLI tools exist, add explicit Linux/macOS installation and usage instructions.
  • For GitHub Actions and Azure DevOps, include Linux/macOS runner examples and clarify any platform-specific limitations.
  • If PowerShell is required, note whether PowerShell Core (pwsh) on Linux/macOS is supported, and provide corresponding examples.
  • For each integration, provide parity in examples and setup steps for Linux/macOS where possible, or clearly state if not supported.
GitHub Create Pull Request
Artifact Signing Sign a CI policy by using Artifact Signing ...ain/articles/artifact-signing/how-to-sign-ci-policy.md
High Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows, requiring Azure PowerShell and providing only PowerShell-based examples with Windows-style file paths. Prerequisites and instructions assume a Windows environment, with no mention of Linux/macOS alternatives or cross-platform usage. The deployment section exclusively references Windows Defender Application Control, further reinforcing the Windows-centric approach.
Recommendations
  • Provide equivalent instructions and examples for Linux/macOS users, including bash or shell commands where possible.
  • Clarify whether Az.TrustedSigning and related modules can be used on non-Windows platforms, and document installation steps for those platforms.
  • Use cross-platform file path examples or note differences for Linux/macOS (e.g., /tmp/root.cer).
  • Include guidance for signing and deploying CI policies in non-Windows environments, if supported.
  • Add links to relevant Linux/macOS documentation or tools, if available.
GitHub Create Pull Request
Artifact Signing Device Guard Signing Service migration to Artifact Signing ...gning/how-to-device-guard-signing-service-migration.md
High Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily Windows-centric, with all examples, tools, and instructions tailored exclusively for Windows environments. It references Windows-specific directories, PowerShell cmdlets, and tools like SignTool and MSIX Packaging Tool, with no mention of Linux or macOS equivalents or workflows. The migration and deployment steps assume Windows OS and do not provide guidance for cross-platform scenarios.
Recommendations
  • Add explicit notes about platform support and limitations, clarifying whether Artifact Signing and CI policies are Windows-only or if Linux/macOS are supported.
  • If Linux/macOS support exists, provide equivalent instructions for those platforms, including directory paths, command-line tools, and deployment steps.
  • Where PowerShell is used, offer Bash or shell script alternatives for Linux/macOS users.
  • Reference cross-platform signing tools if available, or clarify that SignTool and MSIX Packaging Tool are Windows-only.
  • Restructure examples to either be platform-neutral or to present Linux/macOS instructions alongside Windows ones, rather than Windows-first.
  • Include troubleshooting and verification steps for non-Windows platforms if supported.
GitHub 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 →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page is heavily focused on Windows, with all detailed setup instructions and examples tailored exclusively for Windows environments. It relies on Windows-specific tools (SignTool.exe, MSI installers, winget, PowerShell), and does not provide equivalent instructions or examples for Linux or macOS users. Linux/macOS users are left without guidance for setting up Artifact Signing, especially for the SignTool integration.
Recommendations
  • Provide explicit instructions for Linux/macOS users, including supported signing tools and setup steps.
  • Include examples for cross-platform tools (e.g., OpenSSL, osslsigncode, or platform-agnostic SDK usage) where possible.
  • If SignTool is Windows-only, clarify alternative signing workflows for Linux/macOS users using Artifact Signing SDK or other integrations.
  • List Linux/macOS compatible installers and commands (e.g., .NET runtime installation via apt, yum, or brew).
  • Ensure parity in authentication and configuration examples for non-Windows platforms.
GitHub 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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias, especially in the SignTool integration section. All setup instructions, prerequisites, and examples are exclusively for Windows environments, using Windows-specific tools (SignTool.exe, MSI installers, WinGet, PowerShell). There are no Linux or macOS equivalents, nor any mention of cross-platform alternatives for direct signing. Other integrations (GitHub Actions, Azure DevOps) are referenced only via external links, without parity in detailed setup instructions.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, including supported signing tools and workflows.
  • If SignTool is Windows-only, clarify this limitation and provide alternative signing methods for non-Windows platforms (e.g., OpenSSL, GPG, or cross-platform SDK usage).
  • Include parity in setup walkthroughs for GitHub Actions and Azure DevOps, showing how Linux/macOS runners can use Artifact Signing.
  • List platform compatibility for each integration at the top of the page.
  • Provide a table summarizing which integrations are cross-platform and which are Windows-only.
GitHub Create Pull Request
Artifact Signing Device Guard Signing Service migration to Artifact Signing ...gning/how-to-device-guard-signing-service-migration.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
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) specific to Windows. There are no Linux or macOS equivalents or instructions, nor is there any mention of how to perform migration or signing tasks on non-Windows platforms. Windows file paths, registry, and deployment guides are referenced exclusively.
Recommendations
  • Add explicit guidance for Linux/macOS users, including whether Artifact Signing supports non-Windows CI policies and how to manage them.
  • Provide cross-platform command-line examples (e.g., Bash, Azure CLI) for key steps such as signing, verification, and deployment.
  • Clarify platform requirements and limitations at the start of the document.
  • If Windows-only, state this clearly and provide links to relevant Linux/macOS documentation if available.
  • Include alternative tools or workflows for Linux/macOS environments, or note if such workflows are unsupported.
GitHub Create Pull Request
Artifact Signing Sign a CI policy by using Artifact Signing ...ain/articles/artifact-signing/how-to-sign-ci-policy.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows, requiring Azure PowerShell and providing only PowerShell-based examples with Windows-style paths. There are no instructions or examples for Linux or macOS users, and all referenced tools and deployment guides are Windows-specific.
Recommendations
  • Provide equivalent CLI instructions for Linux/macOS environments, such as using PowerShell Core on Linux or Azure CLI if supported.
  • Include examples with Linux/macOS file paths and clarify cross-platform compatibility of the Az.TrustedSigning module.
  • Explicitly state OS requirements and offer alternatives or workarounds for non-Windows users.
  • Reference deployment guides or documentation relevant to Linux/macOS if available, or clarify Windows-only scope.
GitHub Create Pull Request
Artifact Signing Device Guard Signing Service migration to Artifact Signing ...gning/how-to-device-guard-signing-service-migration.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily Windows-centric, focusing exclusively on Windows Defender Application Control (WDAC) and Device Guard, which are Windows-only technologies. All examples, commands, and file paths use Windows conventions (e.g., C:\Windows\System32\CodeIntegrity, PowerShell cmdlets like ConvertFrom-CIPolicy, and tools like SignTool and mountvol.exe). There are no Linux/macOS equivalents, nor any mention of how to perform similar tasks on non-Windows platforms. The migration steps, verification, and deployment instructions are all tailored for Windows environments, leaving Linux/macOS users without guidance or support.
Recommendations
  • Explicitly state that the process and tooling are Windows-only, and clarify the lack of Linux/macOS support.
  • If Artifact Signing supports non-Windows platforms, add equivalent examples for Linux/macOS (e.g., using OpenSSL, Linux file paths, bash commands).
  • Provide guidance or references for code integrity and signing on Linux/macOS, if applicable.
  • If the service is Windows-only, add a prominent note at the top of the documentation to inform non-Windows users.
  • Consider including a comparison table of platform support for Artifact Signing and related features.
GitHub Create Pull Request
Artifact Signing Sign a CI policy by using Artifact Signing ...ain/articles/artifact-signing/how-to-sign-ci-policy.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows, requiring Azure PowerShell and giving only PowerShell-based examples with Windows-style paths. There are no Linux/macOS instructions, and all referenced tools and deployment guides are Windows-specific.
Recommendations
  • Provide equivalent instructions for Linux/macOS, including installation of Azure PowerShell on those platforms.
  • Show examples using bash or cross-platform PowerShell (with Linux/macOS file paths).
  • Clarify whether Az.TrustedSigning and related commands work on Linux/macOS, and document any platform-specific limitations.
  • Include links or guidance for Linux/macOS users on creating and deploying CI policies, if supported.
  • Avoid assuming Windows file system conventions (e.g., use /tmp/ instead of C:\temp\ in examples).
GitHub 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 →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page is heavily biased toward Windows, focusing exclusively on Windows tools (SignTool.exe, MSI installers, WinGet, PowerShell) with no mention of Linux or macOS equivalents or setup instructions. All examples and installation methods are Windows-specific, and prerequisites require Windows OS. Linux and macOS users are left without guidance for using Artifact Signing directly, except possibly via CI/CD integrations like GitHub Actions or Azure DevOps, which are only briefly referenced.
Recommendations
  • Add explicit instructions and examples for Linux and macOS users, including supported signing tools and setup steps.
  • Clarify whether Artifact Signing can be used outside Windows, and if so, provide parity for SDK, dlib, and runtime installation on non-Windows platforms.
  • Include cross-platform examples for signing artifacts, such as using .NET CLI, OpenSSL, or other common Linux/macOS tools.
  • If SignTool is Windows-only, highlight alternative signing workflows for Linux/macOS (e.g., via GitHub Actions, Azure DevOps, or SDK usage).
  • Reorganize the documentation to present cross-platform options first, or in parallel, rather than focusing on Windows tools and patterns.
GitHub Create Pull Request