Repository navigation
Description
What's going on?
@playwright/cli@0.1.19 no longer includes npm trusted-publisher or Sigstore/SLSA provenance metadata. This is a regression from 0.1.18 and causes package managers that enforce supply-chain trust continuity to reject the update as a trust downgrade.
This appears related to microsoft/playwright-cli#456, which moved stable npm publishing from GitHub Actions OIDC to the Microsoft ESRP pipeline.
Metadata comparison
0.1.18 was published by GitHub Actions and includes _npmUser.trustedPublisher, dist.attestations with SLSA provenance, and gitHead:
{
"version": "0.1.18",
"gitHead": "ca196c297169a494ee5517584883eada60dc8d0e",
"_npmUser": {
"name": "GitHub Actions",
"trustedPublisher": { "id": "github" }
},
"dist": {
"attestations": {
"provenance": { "predicateType": "https://slsa.dev/provenance/v1" }
}
}
}0.1.19 was published by microsoft1es and contains none of those fields:
{
"version": "0.1.19",
"gitHead": null,
"_npmUser": {
"name": "microsoft1es",
"email": "npmjs@microsoft.com"
},
"dist": { "attestations": null }
}The canonical npm attestation endpoint demonstrates the regression:
curl -o /dev/null -w '%{http_code}\n' \
'https://registry.npmjs.org/-/npm/v1/attestations/%40playwright%2Fcli@0.1.18'
# 200
curl -o /dev/null -w '%{http_code}\n' \
'https://registry.npmjs.org/-/npm/v1/attestations/%40playwright%2Fcli@0.1.19'
# 404Reproduction
Using mise 2026.9.0, whose npm backend enforces Aube's no-downgrade trust policy:
mise install npm:@playwright/cli@latestfails with:
trust downgrade for @playwright/cli@0.1.19 (trustPolicy=no-downgrade):
earlier published version 0.1.0 had trusted publisher but this version has no trust evidence
The exact dependencies pinned by 0.1.19 have the same issue:
playwright@1.63.0-alpha-2026-08-31playwright-core@1.63.0-alpha-2026-08-31
Their npm attestation endpoints also return 404, so restoring provenance only for the top-level CLI package would not make strict installations succeed.
Expected behavior
Stable releases should retain public, machine-verifiable provenance. Would it be possible to either:
- configure the ESRP publishing path to emit npm trusted-publisher/Sigstore provenance; or
- retain the previous GitHub Actions OIDC workflow for stable npm releases until ESRP can provide equivalent public attestations?
The pinned playwright and playwright-core packages would also need equivalent provenance.
Additional verification
I am not reporting evidence of package tampering. I verified that:
v0.1.19is an official GitHub release;- the release commit is verified;
- every file in the npm tarball matches the corresponding file at the
v0.1.19source tag byte-for-byte; and - the downloaded tarball matches npm's published SHA-1 and SHA-512 integrity values.
The concern is specifically the loss of machine-verifiable source-to-package provenance and the resulting compatibility regression for strict package installers.
The Playwright maintainers previously confirmed that microsoft1es and the missing metadata were expected during the publishing migration in microsoft/playwright#42144. This report is about the downstream impact now that the migration also covers stable @playwright/cli releases.
Version
@playwright/cli@0.1.19 (with playwright@1.63.0-alpha-2026-08-31 and playwright-core@1.63.0-alpha-2026-08-31)
Activity
Merge pull request #1148 from Chelydra-Labs/chore/deps-frontend-minor…