chore(package): package.json has no license field although the repo ships an MIT LICENSE
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 86/100
Research direction
Open package.json at the repository root and LICENSE side by side; confirm the LICENSE text is MIT, then add "license": "MIT" to the package metadata. The reported repro reads the field back through the GitHub contents API, so re-running it should print MIT instead of None. If you follow the TDD plan, first find the existing test setup in the repo and add a small assertion that parses package.json and compares its license value to the identifier in LICENSE, then run the suite to confirm nothing else broke. Done means the field is present, matches the LICENSE file, and all tests pass.
Written by the indexing model from the issue text.
Description
Problem
flisk-sh/analytics ships an MIT LICENSE file, but its package.json has no license field. Tools that read package metadata (npm, license scanners, SBOM generators, dependency dashboards) report the package as "UNLICENSED" or "unknown" even though the repo is MIT.
Repro:
gh api repos/flisk-sh/analytics/contents/package.json --jq .content | base64 -d | python3 -c "import sys,json; print(json.load(sys.stdin).get('license'))"
# None
Root Cause Analysis
The LICENSE file was added, but the matching SPDX identifier was never written into package.json.
TDD Fix Plan
- RED: Add a test that parses
package.jsonand assertslicenseequals the SPDX id in theLICENSEfile (MIT).
GREEN: Add"license": "MIT"topackage.json.
REFACTOR: None expected.
Acceptance Criteria
-
package.jsonhas"license": "MIT" - It matches the
LICENSEfile - All new tests pass
- Existing tests still pass
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 2
- Avg merge
- 1h 33m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from flisk-sh/analytics
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
All issues in flisk-sh/analytics
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
needs:triage
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
fix(readme): skills.sh badge says 'resource not found' and the skills.sh link is a 404; skills.sh still lists the old name tdk-skillsPossibly taken @bfs2021 claimed this today. Openarea: ci area: docs badge bug chore cleanup consistency developer-experience difficulty: easy docs documentation good first issue hygiene journey: first-visit links priority: P3 skills user-journey
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
flisk-sh/flisk-skills#39 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Ionaru/easy-markdown-editor#656 ·