Repository navigation
What's in it
0.2.2 is about how a release is produced and checked, not about new tools: the bundle can now be signed, and every published release is re-derived from its tag by CI instead of being taken on trust.
A signed bundle
playwright-e2e-mcp-0.2.2.signed.mcpb is the reproducible bundle plus a PKCS#7 signature block. The unsigned bundle is still published and is still the artifact to reproduce — mcpb unsign on the signed file returns its exact bytes, which is asserted on every signing run and re-checked by this release's own verification.
- Signer:
CN=playwright-e2e-mcp, O=trajectiq-ai, C=US - SHA-256 fingerprint:
53:83:ED:DD:9A:48:5E:D3:39:24:6D:37:12:BD:56:CC:FD:40:47:D8:14:03:CE:8D:BD:EB:C2:3E:4C:7A:B9:22 - The certificate is published as
playwright-e2e-mcp-signing-cert.pem. The private key is not in the repository and never leaves the machine that signs.
What "signed" means here is decided by the certificate. mcpb verify and mcpb info only accept a signature when the certificate chains into the OS trust store, so with this self-signed certificate a host still reports Not signed until you install it. That is integrity and key continuity, not third-party identity; a CA-issued certificate is what changes a host's answer.
The signature is nevertheless real and verifiable without trusting anything — checked against this exact artifact:
# pull the PKCS#7 block out of the signed bundle
node -e "const fs=require('fs');const s=fs.readFileSync('playwright-e2e-mcp-0.2.2.signed.mcpb');const h=Buffer.from('MCPB_SIG_V1'),f=Buffer.from('MCPB_SIG_END');const fi=s.lastIndexOf(f),hi=s.lastIndexOf(h,fi),n=s.readUInt32LE(hi+h.length);fs.writeFileSync('sig.der',s.subarray(hi+h.length+4,hi+h.length+4+n));fs.writeFileSync('content.mcpb',s.subarray(0,hi));"
openssl smime -verify -inform DER -in sig.der -content content.mcpb \
-CAfile playwright-e2e-mcp-signing-cert.pem -purpose any -out /dev/null
# Verification successful (exit 0)
# a byte changed in content.mcpb → digest failure (exit 4)
# any other certificate as -CAfile → signature failure (exit 1)And content.mcpb above is byte-identical to playwright-e2e-mcp-0.2.2.mcpb.
Releases verify themselves
.github/workflows/verify-release.yml now runs on every published release. It checks that the tag matches package.json, that the published bundle is byte-identical to a fresh npm run mcpb, that .mcpb.sha256 and SHA256SUMS.txt agree with every asset (and cover all of them), that the signed bundle strips back to the reproducible bytes, that the published archive still extracts with this version's manifest — and then drives the published file with the official MCP SDK client. Run it on demand for any past tag from Actions → Verify release → Run workflow.
Assets
| asset | what it is |
|---|---|
playwright-e2e-mcp-0.2.2.mcpb |
the bundle — byte-reproducible across platforms |
playwright-e2e-mcp-0.2.2.signed.mcpb |
the same bundle plus a PKCS#7 signature |
playwright-e2e-mcp-0.2.2.tgz |
the exact artifact published to npm, with provenance |
playwright-e2e-mcp-signing-cert.pem |
the public certificate the signature chains to |
SHA256SUMS.txt |
hashes of everything above |
*.mcpb.sha256 |
each bundle, plus the lockfile hash it was built from |
sha256sum -c SHA256SUMS.txtReproducing the bundle
git clone https://github.com/trajectiq-ai/E2E && cd E2E
git checkout v0.2.2
npm ci && npm run mcpb
sha256sum playwright-e2e-mcp-0.2.2.mcpb
# 547c3dff0bd62a67bd8cd4b9f13446e7a15eb62015c7e598bbe9fc349c7cfa9cOr in one command, from a checkout of the tag: npm run release:verify -- v0.2.2.
Changed
- Version →
0.2.2inpackage.json,package-lock.jsonandserver.json; README pins and the documented download URL move tov0.2.2. - README demo image regenerated so the endpoint card shows the released version.
npm run mcpb:signandnpm run release:verifyare the two new entry points; the private key is read only from a path you pass in (--cert/--keyorMCPB_CERT/MCPB_KEY) and error messages never echo it.