Check and fix Apache 2.0 license headers and dependency licenses using skywalking-eyes. Use before submitting a PR.
74
92%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Check and fix license compliance using skywalking-eyes. Two CI jobs use this tool:
check argument)license-eye header checkvalid: N, invalid: 0 — nothing to do.license-eye header fix, then re-check.fix argument)license-eye header fix
license-eye header checkdeps argument)This regenerates the LICENSE file from dependency metadata and checks for drift:
license-eye dependency resolve --summary ./dist-material/release-docs/LICENSE.tpl || exit 1
if [ ! -z "$(git diff -U0 ./dist-material/release-docs/LICENSE)" ]; then
echo "LICENSE file is not updated correctly"
git diff -U0 ./dist-material/release-docs/LICENSE
fiIf the LICENSE file changed, review the diff and commit it. Important: CI runs on Linux — some dependencies have platform-specific variants. If you're on macOS/Windows, the LICENSE diff may be a platform artifact. Verify before committing.
Configuration is in .licenserc.yaml:
META-INF/services/) require headers (use # comment style)# Same version as CI (pinned commit)
go install github.com/apache/skywalking-eyes/cmd/license-eye@5b7ee1731d036b5aac68f8bd3fc9e6f98ada082e
# Or via Homebrew (macOS)
brew install license-eyebf0fe4b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.