Skip to content

fix(ci): allow modernc.org/libc NOASSERTION license in dependency review#473

Merged
ajitpratap0 merged 1 commit intomainfrom
fix/license-detection
Mar 29, 2026
Merged

fix(ci): allow modernc.org/libc NOASSERTION license in dependency review#473
ajitpratap0 merged 1 commit intomainfrom
fix/license-detection

Conversation

@ajitpratap0
Copy link
Copy Markdown
Owner

Summary

Test plan

  • Dependency Review check passes on this PR
  • Future PRs adding modernc.org deps no longer fail license check

🤖 Generated with Claude Code

modernc.org/libc is BSD-3-Clause but GitHub's license detection reports
NOASSERTION due to a detection failure on modernc.org packages. Adding
LicenseRef-github-NOASSERTION to the allow-licenses list prevents false
positive CI failures on PRs that depend on modernc.org/sqlite.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel bot commented Mar 29, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
gosqlx-website Ready Ready Preview, Comment Mar 29, 2026 1:13pm

@github-actions github-actions bot added the ci-cd label Mar 29, 2026
@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 29, 2026

Claude finished @ajitpratap0's task —— View job


PR Review Complete

I've reviewed this pull request focusing on code quality, security concerns, and best practices.

Todo List:

  • Read and analyze the security workflow changes
  • Assess security implications of allowing NOASSERTION licenses
  • Check workflow syntax and configuration
  • Provide comprehensive review feedback

Review Feedback

✅ Code Quality and Best Practices

Positive aspects:

  • Clear documentation: The change includes helpful inline comments explaining why modernc.org/libc reports NOASSERTION despite being BSD-3-Clause
  • Targeted fix: The change is specific to the problematic package rather than broadly allowing all NOASSERTION licenses
  • Proper formatting: Uses YAML block scalar (>-) for multi-line license list with proper indentation
  • Workflow syntax: All YAML syntax is correct and follows GitHub Actions conventions

⚠️ Security Considerations

The change has acceptable security risk:

Low Risk Assessment:

  • The added license LicenseRef-github-NOASSERTION specifically addresses a known GitHub license detection failure
  • The dependency modernc.org/libc is actually BSD-3-Clause licensed (permissive, open-source)
  • This is a targeted allowlist addition, not a blanket approval of unknown licenses
  • The existing workflow still blocks packages with genuinely problematic licenses

Recommendation:Approve with monitoring

  • The change is safe for this specific use case
  • Consider adding a periodic review process to verify that packages with NOASSERTION are still legitimate

📋 Suggestions for Improvement

  1. Documentation Enhancement (.github/workflows/security.yml:174-175):

    # modernc.org/libc is BSD-3-Clause but GitHub reports NOASSERTION
    # due to license detection failure on the modernc.org packages.
    # TODO: Remove this exception if GitHub fixes license detection
  2. Future Monitoring: Consider creating a separate issue to track and periodically verify that dependencies using NOASSERTION are still legitimate.

🔍 Performance Considerations

No performance impact: This change only affects the dependency review action's license validation logic and doesn't impact runtime performance.

🧪 Test Coverage

Workflow testing:

  • The PR will test the change automatically when the dependency review job runs
  • The test plan in the PR description correctly identifies the validation steps

📊 Overall Assessment

This is a well-implemented, targeted fix for a specific GitHub license detection issue. The security risk is minimal since:

  • The actual license is known (BSD-3-Clause)
  • The change is documented with context
  • The fix is specific rather than overly permissive

Recommendation: ✅ APPROVE

The change appropriately addresses the stated problem without introducing significant security risks.


@ajitpratap0 ajitpratap0 merged commit 384a825 into main Mar 29, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant