microsoft / microsoft/playwright-dotnet
[BUG] Unsigned artifacts in Playwright NuGet package
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3k
- Forks
- 304
- Avg merge
- 20h 47m
- Merged PRs (30d)
- 6
Description
Context:
- Playwright Version: 1.22.0, verified with 1.35.0 as well)
- Operating System: Windows, Linux
- .NET version: .net 4.8, .NET 6
- Browser: N/A
- Extra: [any specific details about your environment]
Describe the bug
Following up to #2569, it appears that there are several other artifacts within the playwright nuget package that are not digitally signed. Among them are the PrintDeps.exe executable and all of the PowerShell scripts included in the .playwright folder. Due to this we are unable to ship our application that consumes Playwright as we are unable to ship unsigned artifacts in our deliverables. Please feel free to reach out for any questions or more information!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the Playwright NuGet package contents, especially PrintDeps.exe and the PowerShell scripts in the .playwright folder, then trace the packaging and signing process. Done means these artifacts are digitally signed and the resulting package can be consumed in deliverables that reject unsigned files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- release, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100