Latest Threat Research:SANDWORM_MODE: Shai-Hulud-Style npm Worm Hijacks CI Workflows and Poisons AI Toolchains.Details
Socket
Book a DemoInstallSign in
Socket

@flakiness/playwright

Package Overview
Dependencies
Maintainers
1
Versions
13
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@flakiness/playwright - npm Package Compare versions

Comparing version
1.1.0
to
1.1.1
+2
-2
package.json
{
"name": "@flakiness/playwright",
"version": "1.1.0",
"version": "1.1.1",
"private": false,

@@ -40,3 +40,3 @@ "repository": {

"@flakiness/flakiness-report": "^0.25.0",
"@flakiness/sdk": "1.1.0",
"@flakiness/sdk": "2.0.0",
"chalk": "^5.6.2"

@@ -43,0 +43,0 @@ },

@@ -17,2 +17,3 @@ # Flakiness.io Playwright Reporter

- [Configuration Options](#configuration-options)
- [`flakinessProject?: string`](#flakinessproject-string)
- [`endpoint?: string`](#endpoint-string)

@@ -66,4 +67,9 @@ - [`token?: string`](#token-string)

Reports are automatically uploaded to Flakiness.io in the `onExit()` hook if a valid access token is provided (via `token` option or `FLAKINESS_ACCESS_TOKEN` environment variable).
Reports are automatically uploaded to Flakiness.io in the `onExit()` hook. Authentication can be done in two ways:
- **Access token**: Provide a token via the `token` option or the `FLAKINESS_ACCESS_TOKEN` environment variable.
- **GitHub OIDC**: When running in GitHub Actions, the reporter can authenticate using GitHub's OIDC token — no access token needed. This requires two conditions:
1. The `flakinessProject` option must be set to your Flakiness.io project identifier (`org/project`).
2. The Flakiness.io project must be bound to the GitHub repository that runs the GitHub Actions workflow.
If upload fails, the report is still available locally in the output folder.

@@ -131,2 +137,12 @@

### `flakinessProject?: string`
The Flakiness.io project identifier in `org/project` format. Used for GitHub OIDC authentication — when set, and the Flakiness.io project is bound to the GitHub repository running the workflow, the reporter authenticates uploads via GitHub Actions OIDC token with no access token required.
```typescript
reporter: [
['@flakiness/playwright', { flakinessProject: 'my-org/my-project' }]
]
```
### `endpoint?: string`

@@ -212,2 +228,3 @@

['@flakiness/playwright', {
flakinessProject: 'my-org/my-project',
endpoint: process.env.FLAKINESS_ENDPOINT,

@@ -214,0 +231,0 @@ token: process.env.FLAKINESS_ACCESS_TOKEN,