Skip to content

Eclipse/Solar Analysis Plugin #1144

Eclipse/Solar Analysis Plugin

Eclipse/Solar Analysis Plugin #1144

Triggered via pull request November 16, 2025 23:24
Status Success
Total duration 7m 47s
Artifacts

build-pipeline.yml

on: pull_request
Yaml Lint
15s
Yaml Lint
NPM Audit Report
23s
NPM Audit Report
Matrix: Lint and Unit Tests
TruffleHog Secrets Scan
1m 3s
TruffleHog Secrets Scan
CodeQL Security Scan
2m 39s
CodeQL Security Scan
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 13 warnings
Yaml Lint
Process completed with exit code 1.
NPM Audit Report
CodeQL Security Scan
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
Lint and Unit Tests (eslint): src/plugins-pro/initial-orbit/om-manager.ts#L342
Blocks are nested too deeply (5). Maximum allowed is 4
Lint and Unit Tests (eslint): src/plugins-pro/initial-orbit/om-manager.ts#L329
Blocks are nested too deeply (6). Maximum allowed is 4
Lint and Unit Tests (eslint): src/plugins-pro/initial-orbit/om-manager.ts#L326
Blocks are nested too deeply (5). Maximum allowed is 4
Lint and Unit Tests (eslint): src/keepTrackApi.ts#L101
Unexpected console statement
Lint and Unit Tests (eslint): src/engine/rendering/gl-utils.ts#L62
Unexpected console statement
Lint and Unit Tests (eslint): src/engine/input/url-manager.ts#L644
Unexpected console statement
Lint and Unit Tests (eslint): src/engine/input/url-manager.ts#L256
Unexpected console statement
CodeQL Security Scan
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
CodeQL Security Scan
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.23.5.
CodeQL Security Scan
This run of the CodeQL Action does not have permission to access the CodeQL Action API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the workflow has at least the 'security-events: read' permission. Details: Resource not accessible by integration - https://docs.github.com/rest