Flame confuses mit-modern with MIT-Modern-Variant

Open
#266 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
databases

Research direction

Start by tracing how the license records and aliases for mit-modern and MIT-Modern-Variant are stored and used by the flame CLI. Compare their metadata to determine whether they represent the same license; update the alias or records accordingly, then rerun both commands from the issue and confirm their reported identification keys are correct.

Written by the indexing model from the issue text.

Description

Flame confuses mit-modern with MIT-Modern-Variant (see below)

  • if it is the same license, remove alias
  • if separate licenses, fix the aliases
$ flame -of json license mit-modern
{
    "queried_license": "mit-modern",
    "identified_license": "mit-modern",
    "identified_license_scancode_key": "mit-modern",
    "identifications": [],
    "ambiguities": [],
    "updated_license": "mit-modern",
    "license_parsed": "mit-modern",
    "updates": []
}
$ flame -of json license MIT-Modern-Variant
{
    "queried_license": "MIT-Modern-Variant",
    "identified_license": "MIT-Modern-Variant",
    "identified_license_scancode_key": "mit-modern",
    "identifications": [],
    "ambiguities": [],
    "updated_license": "MIT-Modern-Variant",
    "license_parsed": "MIT-Modern-Variant",
    "updates": []
}
Dominant language
Python
Stars
7
Forks
3
Avg merge
2h 53m
Merged PRs (30d)
7

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/foss-licenses

All issues in aboutcode-org/foss-licenses

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.