Skip to content

Add CodeQL analysis workflow#47

Merged
san360 merged 1 commit into
mainfrom
aymenfurter/animated-telegram
May 25, 2026
Merged

Add CodeQL analysis workflow#47
san360 merged 1 commit into
mainfrom
aymenfurter/animated-telegram

Conversation

@aymenfurter
Copy link
Copy Markdown
Contributor

Adds automated CodeQL code scanning for JavaScript/TypeScript.

What this does:

  • Scans on push to main, PRs targeting main, and weekly (Mondays at 03:25 UTC)
  • Uses minimal permissions (contents: read, security-events: write)
  • Results are visible only to repo admins/writers in the Security tab

Why:
Proactive vulnerability detection for the TypeScript codebase.

Configures automated code scanning on push to main, pull requests,
and a weekly schedule (Mondays at 03:25 UTC).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions
Copy link
Copy Markdown

⚠️ Deprecation Warning: The deny-licenses option is deprecated for possible removal in the next major release. For more information, see issue 997.

Dependency Review

The following issues were found:
  • ✅ 0 vulnerable package(s)
  • ✅ 0 package(s) with incompatible licenses
  • ✅ 0 package(s) with invalid SPDX license definitions
  • ⚠️ 4 package(s) with unknown licenses.
See the Details below.

License Issues

.github/workflows/codeql.yml

PackageVersionLicenseIssue Type
actions/checkout6.*.*NullUnknown License
github/codeql-action/analyze3.*.*NullUnknown License
github/codeql-action/autobuild3.*.*NullUnknown License
github/codeql-action/init3.*.*NullUnknown License
Denied Licenses: GPL-3.0, AGPL-3.0

OpenSSF Scorecard

PackageVersionScoreDetails
actions/actions/checkout 6.*.* 🟢 5.7
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained⚠️ 01 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Binary-Artifacts🟢 10no binaries found in the repo
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Packaging⚠️ -1packaging workflow not detected
Pinned-Dependencies🟢 3dependency not pinned by hash detected -- score normalized to 3
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Security-Policy🟢 9security policy file detected
Branch-Protection🟢 5branch protection is not maximal on development and all release branches
SAST🟢 8SAST tool detected but not run on all commits
actions/github/codeql-action/analyze 3.*.* UnknownUnknown
actions/github/codeql-action/autobuild 3.*.* UnknownUnknown
actions/github/codeql-action/init 3.*.* UnknownUnknown

Scanned Files

  • .github/workflows/codeql.yml

@github-advanced-security
Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@aymenfurter aymenfurter added the security Security-related issue label May 24, 2026
@aymenfurter aymenfurter assigned aymenfurter and unassigned san360 May 25, 2026
@aymenfurter aymenfurter requested a review from san360 May 25, 2026 12:37
@san360 san360 merged commit acc68cf into main May 25, 2026
6 checks passed
@san360 san360 deleted the aymenfurter/animated-telegram branch May 25, 2026 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

security Security-related issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants