chore(package): package.json has no license field although the repo ships an MIT LICENSE

Open Beginner friendly
#19 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
86/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
node.js
Domain
release

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

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

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

  1. RED: Add a test that parses package.json and asserts license equals the SPDX id in the LICENSE file (MIT).
    GREEN: Add "license": "MIT" to package.json.

REFACTOR: None expected.

Acceptance Criteria

  • package.json has "license": "MIT"
  • It matches the LICENSE file
  • 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

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 flisk-sh/analytics

All issues in flisk-sh/analytics

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.