Skip to content

Missing license information for repositories due to unrecognized license filename #194

Closed

Description

@chinyeungli

Projects under aboutcode-org are lacking license information in the 'About' section.
In addition, the github API responses do not provide license details (e.g., license: null)
For instance,
https://api.github.com/repos/aboutcode-org/purldb
https://api.github.com/repos/aboutcode-org/scancode-toolkit

This happens because GitHub does not recognize apache-2.0.LICENSE as a valid license file. It only looks for files named LICENSE, LICENSE.md etc. Since the project repositories don't have these files, GitHub is unable to detect the license.

Activity

  1. pombredanne commented on Jul 15, 2025

    @pombredanne
    Member

    @LuciferVid what about fixing GitHub license detection instead?

  2. chinyeungli commented on Jul 15, 2025

    @chinyeungli
    ContributorAuthor

    @LuciferVid Thanks for the effort. I think what @pombredanne meant is that instead of renaming the current license file from apache-2.0.LICENSE to LICENSE, we should explore ways to request github to adjust its license detection behavior.

  3. CodeMaverick-143 commented on Oct 1, 2025

    @CodeMaverick-143

    @chinyeungli is this issue still open , Can I contribute to it ?

  4. CodeMaverick-143 commented on Oct 1, 2025

    @CodeMaverick-143
  5. chinyeungli commented on Oct 1, 2025

    @chinyeungli
    ContributorAuthor

    @LuciferVid Yes. Thanks for the clarification.

  6. vanshika2424agr commented on Dec 14, 2025

    @vanshika2424agr

    @chinyeungli is this issue still open? can i have any chance to contribute here?

  7. chinyeungli commented on Dec 14, 2025

    @chinyeungli
    ContributorAuthor

    @vanshika2424agr Thanks for your interest. I’ve already submitted a request to GitHub to update their license detection behavior (https://github.com/orgs/community/discussions/181937), since we don’t want to rely on the renaming approach (see the comments above). At this point, I don’t think there’s anything else that needs to be done.

  8. added a commit that references this issue on Jan 13, 2026
    1a4400c
  9. added a commit that references this issue on Feb 5, 2026
    038de98
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions