Skip to content

Add SPDX license header checker and missing headers - #864

Draft
shreyah963 wants to merge 2 commits into
opensearch-project:mainfrom
shreyah963:add-spdx-license-header-checker
Draft

Add SPDX license header checker and missing headers#864
shreyah963 wants to merge 2 commits into
opensearch-project:mainfrom
shreyah963:add-spdx-license-header-checker

Conversation

@shreyah963

@shreyah963 shreyah963 commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Description

Add SPDX license header validation to PR/push workflows using @kt3k/license-checker.

Changes:

  • Add .github/workflows/license-header-checker.yml
  • Add .licenserc.json
  • Add missing SPDX-License-Identifier: Apache-2.0 headers to source files

Related Issues

#6445

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: shreyah963 <shreyab963@gmail.com>
@github-actions

github-actions Bot commented Aug 26, 2026

Copy link
Copy Markdown

PR Code Analyzer ❗

AI-powered 'Code-Diff-Analyzer' found issues on commit c65ee2b.

Hard block: Issues at High severity or above will block this PR from merging.

PathLineSeverityDescription
.github/workflows/license-header-checker.yml12highSupply chain risk: introduces `npx @kt3k/license-checker@3.2.2` executed directly in CI. Per mandatory flagging rule, any new package dependency must be flagged regardless of apparent legitimacy. An npm package run via npx in CI has full access to the runner environment including secrets.
.github/workflows/license-header-checker.yml10highSuspicious version annotation: `actions/checkout` is pinned to commit `de0fac2e4500dabe0009e67214ff5f5447ce83dd` with comment `# v6`, but `actions/checkout` has no v6 release (latest is v4). The comment is unverifiable against any real release tag, making it impossible to confirm this hash corresponds to the legitimate action. This pattern is consistent with substituting a malicious fork while using a plausible-looking comment.

The table above displays the top 10 most important findings.

Total: 2 | Critical: 0 | High: 2 | Medium: 0 | Low: 0


Pull Requests Author(s): Please update your Pull Request according to the report above.

Repository Maintainer(s): You can bypass diff analyzer by adding label skip-diff-analyzer after reviewing the changes carefully, then re-run failed actions. To re-enable the analyzer, remove the label, then re-run all actions.


⚠️ Note: The Code-Diff-Analyzer helps protect against potentially harmful code patterns. Please ensure you have thoroughly reviewed the changes beforehand.

Thanks.

Signed-off-by: shreyah963 <shreyab963@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant