license field in META files is "unknown"
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 52/100
Research direction
Start with the linked META.json and META.yml entries and trace how this distribution's metadata is generated. Done means both package metadata files identify the module's license instead of reporting "unknown".
Written by the indexing model from the issue text.
Description
When packaging this module for openSUSE's devel:languges:perl, I noticed that the license is set to unknown:
https://metacpan.org/release/BIGPRESH/Data-Censor-0.04/source/META.json#L9
https://metacpan.org/release/BIGPRESH/Data-Censor-0.04/source/META.yml#L11
- Dominant language
- Perl
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Perl/perl5#24942 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
PDLPorters/pdl#561 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/eolang.sty#197 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
radiator-software/p5-net-ssleay#577 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
beyondgrep/website#143 ·