🚪 Quality Gates

fix: TS errors, biome config, Node 20 in CI, vendored engine #22

Sign in to view logs

Triggered via push March 24, 2026 23:08

Wolfe-Jam

main

Status Failure

Total duration 27s

Artifacts –

quality-gates.yml

on: push

📊 Coverage Gate

⚡ Performance Gate

📝 TypeScript Gate

🔒 Security Gate

📋 Quality Gates Summary

Annotations

22 errors and 5 warnings

🧹 Lint Gate

Process completed with exit code 1.

📝 TypeScript Gate: src/background/service-worker.ts#L24

Module '"@/core/types"' has no exported member 'Score'.

📝 TypeScript Gate: src/adapters/platforms.ts#L1192

Property 'defaultBranch' comes from an index signature, so it must be accessed with ['defaultBranch'].

📝 TypeScript Gate: src/adapters/platforms.ts#L1182

Property 'lastUpdated' comes from an index signature, so it must be accessed with ['lastUpdated'].

📝 TypeScript Gate: src/adapters/platforms.ts#L1173

Property 'languages' comes from an index signature, so it must be accessed with ['languages'].

📝 TypeScript Gate: src/adapters/platforms.ts#L1167

Argument of type 'string | undefined' is not assignable to parameter of type 'string'.

📝 TypeScript Gate: src/adapters/platforms.ts#L1153

Property 'license' comes from an index signature, so it must be accessed with ['license'].

📝 TypeScript Gate: src/adapters/platforms.ts#L1138

Property 'topics' comes from an index signature, so it must be accessed with ['topics'].

📝 TypeScript Gate: src/adapters/platforms.ts#L1126

Property 'stars' comes from an index signature, so it must be accessed with ['stars'].

📝 TypeScript Gate: src/adapters/platforms.ts#L1112

Property 'description' comes from an index signature, so it must be accessed with ['description'].

📝 TypeScript Gate: src/adapters/platforms.ts#L1076

'waitForElement' is declared but its value is never read.

src/tests/core.test.ts > Scoring Engine > Platform Scoring > should score unknown platform appropriately: src/tests/core.test.ts#L130

TypeError: createScore is not a function ❯ src/tests/core.test.ts:130:14

src/tests/core.test.ts > Scoring Engine > Platform Scoring > should score codemirror platform appropriately: src/tests/core.test.ts#L130

TypeError: createScore is not a function ❯ src/tests/core.test.ts:130:14

src/tests/core.test.ts > Scoring Engine > Platform Scoring > should score github platform appropriately: src/tests/core.test.ts#L130

TypeError: createScore is not a function ❯ src/tests/core.test.ts:130:14

src/tests/core.test.ts > Scoring Engine > Platform Scoring > should score monaco platform appropriately: src/tests/core.test.ts#L130

TypeError: createScore is not a function ❯ src/tests/core.test.ts:130:14

src/tests/core.test.ts > Scoring Engine > Score Calculation > should provide score breakdown: src/tests/core.test.ts#L130

TypeError: createScore is not a function ❯ src/tests/core.test.ts:130:14

src/tests/core.test.ts > Scoring Engine > Score Calculation > should respect score boundaries: src/tests/core.test.ts#L130

TypeError: createScore is not a function ❯ src/tests/core.test.ts:130:14

src/tests/core.test.ts > Scoring Engine > Score Calculation > should calculate deterministic scores: src/tests/core.test.ts#L130

TypeError: createScore is not a function ❯ src/tests/core.test.ts:130:14

src/tests/core.test.ts > FAF Engine > Context Extraction > should extract context successfully: src/tests/core.test.ts#L63

AssertionError: expected { version: '1.0.0', …(7) } to have property "score" ❯ src/tests/core.test.ts:63:28

src/tests/adapters.test.ts > Chrome API Adapters > ChromeAction > should use correct colors for different score ranges: src/tests/adapters.test.ts#L131

AssertionError: expected "vi.fn()" to be called with arguments: [ { color: '#FF6B35' }, Any<Function> ] Number of calls: 0 ❯ src/tests/adapters.test.ts:131:55

src/tests/adapters.test.ts > Chrome API Adapters > ChromeAction > should update badge with score: src/tests/adapters.test.ts#L107

AssertionError: expected "vi.fn()" to be called with arguments: [ { text: '85%' }, Any<Function> ] Received: 1st vi.fn() call: [ { - "text": "85%", + "text": "", }, - Any<Function>, + [Function anonymous], ] Number of calls: 1 ❯ src/tests/adapters.test.ts:107:42

📋 Quality Gates Summary

Process completed with exit code 1.

🧹 Lint Gate

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

⚡ Performance Gate

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

🔒 Security Gate

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

📝 TypeScript Gate

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

📊 Coverage Gate

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/