Add the LICENSE file that package.json already declares

Open Beginner friendly
#35 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
82/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Domain
documentation

Research direction

Start by checking the existing license declaration in package.json and confirming that no LICENSE file is present. Add a standard MIT LICENSE file using the repository's stated copyright holder and verify that its license name matches package.json and provides the complete attribution text.

Written by the indexing model from the issue text.

Description

Hi — thanks for building opencode-cursor.

package.json declares "license": "MIT", but the repository contains no
LICENSE file, so GitHub reports the project as unlicensed and downstream
users have no full MIT text (with your copyright line) to rely on and
reproduce.

Would you add a standard MIT LICENSE file (e.g. Copyright (c) 2026 Ephraim Duncan) matching the package.json declaration?

Context: I'm building ganja, a Rust behavioral port of opencode
(https://github.com/zchee/ganja-code, Apache-2.0), and I'd like to derive
Cursor protocol knowledge from this plugin with proper MIT attribution in
our THIRD_PARTY_NOTICES. A LICENSE file in the repo makes that attribution
unambiguous for everyone downstream, not just us.

Thanks!

Dominant language
TypeScript
Stars
278
Forks
31
Avg merge
4h 13m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

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 ephraimduncan/opencode-cursor

All issues in ephraimduncan/opencode-cursor

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.