yegor256/judges

`License Compliance` (FOSSA) check fails on every PR — has failed consistently for weeks

Open

#460 opened on Jun 30, 2026

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Ruby (15 forks)github user discovery
bughelp wanted

Repository metrics

Stars
 (7 stars)
PR merge metrics
 (PR metrics pending)

Description

What happens: The License Compliance GitHub status check (FOSSA) fails on every PR in this repository, going back at least to PR #452 (merged 2026-06-17). Confirmed failing on #452, #453, #456, #457, #458, and #459, each reporting "1 issues found" (PR #452 reported "2 issues found"). The check is not required for merge — PRs are merged despite the red status — but it leaves CI permanently red for a check nobody is acting on.

What should happen: Either the underlying FOSSA-flagged license issue should be resolved (whatever dependency/license combination is being flagged), or the check should be removed/made informational if it's not meant to block anything, so PR status pages don't show a persistent unexplained failure.

Contributor guide

Research direction
Identify the FOSSA configuration files and check if the flagged license issue can be resolved by updating or adding a license exception. If not, propose removing or making the check informational.
Tech stack
ruby
Domain
devopsci cd
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70