Feat: Implemented High-Frequency Contract Calls detection #25
mijinummicode-quality.yml
on: pull_request
Code Quality Analysis
18s
Dependency Security Scan
11s
TypeScript Type Checking
27s
Annotations
12 errors and 3 warnings
|
Dependency Security Scan
Process completed with exit code 1.
|
|
Dependency Security Scan
Process completed with exit code 1.
|
|
TypeScript Type Checking:
apps/backend/src/modules/detection/contracts/spike-detection.service.spec.ts#L43
Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha` and then add 'jest' or 'mocha' to the types field in your tsconfig.
|
|
TypeScript Type Checking:
apps/backend/src/modules/detection/contracts/spike-detection.service.spec.ts#L40
Cannot find name 'expect'.
|
|
TypeScript Type Checking:
apps/backend/src/modules/detection/contracts/spike-detection.service.spec.ts#L39
Cannot find name 'expect'.
|
|
TypeScript Type Checking:
apps/backend/src/modules/detection/contracts/spike-detection.service.spec.ts#L38
Cannot find name 'expect'.
|
|
TypeScript Type Checking:
apps/backend/src/modules/detection/contracts/spike-detection.service.spec.ts#L36
Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha` and then add 'jest' or 'mocha' to the types field in your tsconfig.
|
|
TypeScript Type Checking:
apps/backend/src/modules/detection/contracts/spike-detection.service.spec.ts#L35
Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha` and then add 'jest' or 'mocha' to the types field in your tsconfig.
|
|
TypeScript Type Checking:
apps/backend/src/modules/detection/contracts/spike-detection.service.spec.ts#L32
Cannot find name 'expect'.
|
|
TypeScript Type Checking:
apps/backend/src/modules/detection/contracts/spike-detection.service.spec.ts#L31
Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha` and then add 'jest' or 'mocha' to the types field in your tsconfig.
|
|
TypeScript Type Checking:
apps/backend/src/modules/detection/contracts/spike-detection.service.spec.ts#L23
Cannot find name 'beforeEach'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha` and then add 'jest' or 'mocha' to the types field in your tsconfig.
|
|
TypeScript Type Checking:
apps/backend/src/modules/detection/contracts/spike-detection.service.spec.ts#L19
Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha` and then add 'jest' or 'mocha' to the types field in your tsconfig.
|
|
Dependency Security Scan
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 will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Code Quality Analysis
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 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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 Type Checking
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 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|